Prepaid account funds transfer apparatuses, methods and systems

ABSTRACT

The PREPAID ACCOUNT FUNDS TRANSFER APPARATUSES, METHODS AND SYSTEMS (“PAFT”) transform prepaid account invitation requests via PAFT components into scheduled prepaid account transactions. In one embodiment, the PAFT obtains, from a transferor user holding a transferor prepaid account, a prepaid account invitation request specifying a transferee user and a prepaid funds transfer amount. The PAFT generates a customized prepaid account invitation for the transferee user based on the prepaid account invitation request, and provides the customized prepaid account invitation for the transferee user. Upon obtaining an invitation acceptance from the transferee user in response to the provided customized prepaid account invitation, the PAFT creates a transferee prepaid account for the transferee user, and transfers, upon creating the transferee prepaid account, the prepaid funds transfer amount of funds specified in the prepaid account invitation request from the transferor prepaid account to the created transferee prepaid account.

RELATED APPLICATIONS

Applicant hereby claims priority under 35 USC §119 for U.S. provisionalpatent application Ser. No. 61/304,594 filed Feb. 15, 2010, entitled“PREPAID ACCOUNT TRANSFEROR INVITATION FOR A TRANSFEREE LINKED PREPAIDACCOUNT,”. The entire contents of the aforementioned application areherein expressly incorporated by reference.

This patent application disclosure document (hereinafter “description”and/or “descriptions”) describes inventive aspects directed at variousnovel innovations (hereinafter “innovation,” “innovations,” and/or“innovation(s)”) and contains material that is subject to copyright,mask work, and/or other intellectual property protection. The respectiveowners of such intellectual property have no objection to the facsimilereproduction of the patent disclosure document by anyone as it appearsin published Patent Office file/records, but otherwise reserve allrights.

FIELD

The present inventions are directed generally to apparatuses, methods,and systems for account-based transactions, and more particularly, toPREPAID ACCOUNT FUNDS TRANSFER APPARATUSES, METHODS AND SYSTEMS(“PAFT”).

BACKGROUND

Many users prefer to engage in account-based transactions, such ascredit or debit transactions, because of the security and conveniencethey provide. Prepaid cards are particularly attractive because theyprovide additional advantages such as spending alerts and controls. Therange of account-based transactions is currently limited in terms of thetypes of transactions possible, and the persons with whom suchtransactions may be conducted.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying appendices and/or drawings illustrate variousnon-limiting, example, inventive aspects in accordance with the presentdisclosure:

FIG. 1 shows a block diagram illustrating example aspects of prepaidaccount funds transfer in some embodiments of the PAFT;

FIG. 2 shows a data flow diagram illustrating an example procedure togenerate a customized invitation for a user to open a new prepaidaccount in some embodiments of the PAFT;

FIGS. 3A-B show logic flow diagrams illustrating example aspects ofgenerating a customized invitation for a user to open a new prepaidaccount in some embodiments of the PAFT, e.g., a Prepaid AccountApplication Invitation (PAAI) component 300;

FIGS. 4A-C show data flow diagrams illustrating an example procedure toregister a new prepaid account for a user in some embodiments of thePAFT;

FIGS. 5A-D show logic flow diagrams illustrating example aspects ofregistering a new prepaid account for a user in some embodiments of thePAFT, e.g., a Prepaid Account Registration (PAR) component 500;

FIGS. 6A-B show data flow diagrams illustrating an example procedure totransfer funds from a prepaid account of a user to a prepaid account ofanother user in some embodiments of the PAFT;

FIG. 7 shows a logic flow diagram illustrating example aspects ofimplementing a transferor user-initiated trigger for prepaid accountfunds transfer in some embodiments of the PAFT, e.g., aTransferor-Initiated Funds Transfer Trigger (Tr-FTT) component 700;

FIG. 8 shows a logic flow diagram illustrating example aspects ofimplementing a transferee user-initiated trigger for prepaid accountfunds transfer in some embodiments of the PAFT, e.g., aTransferee-Initiated Funds Transfer Trigger (Te-FTT) component 800;

FIG. 9 shows a logic flow diagram illustrating example aspects ofimplementing a server-initiated trigger for prepaid account fundstransfer in some embodiments of the PAFT, e.g., a Server-Initiated FundsTransfer Trigger (S-FTT) component 900;

FIGS. 10A-C show logic flow diagrams illustrating example aspects oftransferring funds from a prepaid account of a user to a prepaid accountof another user in some embodiments of the PAFT, e.g., a Prepaid AccountFunds Transfer Processing (PA-FTP) component 1000;

FIG. 11 shows a user interface diagram illustrating example aspects ofmanaging prepaid account funds transfers in some embodiments of thePAFT; and

FIG. 12 shows a block diagram illustrating embodiments of a PAFTcontroller.

The leading number of each reference number within the drawingsindicates the figure in which that reference number is introduced and/ordetailed. As such, a detailed discussion of reference number 101 wouldbe found and/or introduced in FIG. 1. Reference number 201 is introducedin FIG. 2, etc.

DETAILED DESCRIPTION Prepaid Account Funds Transfer (PAFT)

The PREPAID ACCOUNT FUNDS TRANSFER APPARATUSES, METHODS AND SYSTEMS(hereinafter “PAFT”) transform prepaid account invitation requests, viavarious PAFT components, into scheduled prepaid account transactions.

FIG. 1 shows a block diagram illustrating example aspects of prepaidaccount funds transfer in some embodiments of the PAFT. In someimplementations, a prepaid account holder, e.g., 101, may owe funds tousers, e.g., 102-104. For example, the prepaid account holder may owefunds for services rendered, e.g., in the example of users 103 and 103.In some scenarios, the user to whom funds are owe may not be able toaccept the funds (see, e.g., in) via account-based transactions such ascredit card payment, for example, because they may not have theinfrastructure to process such transactions as a merchant (e.g.,gardener, repairman). The users may also be unwilling to accept thefunds owed in other forms such as a check, because they may not evenhave a bank account, or because accepting such forms of payment maysubject them to higher levels of risk (see, e.g., 112-113) that theyfind unacceptable, e.g., 116. In some scenarios, such users may be owedfunds on, e.g., a regular, period, basis (see e.g., 114). For example,some services may require that performance be executed more than once,perhaps on a regular repeatable schedule, thus requiring payment on aregular repeatable schedule. In another example, a long schedule ofpayment of funds owed may be pre-determined, exacerbating the problemsof transferring funds owed from the prepaid account holder to theuser(s). In some scenarios, the prepaid account holder may wish totransfer funds (see, e.g., 117) to a user, e.g., 104, but may wish toexercise spending controls on the user for whom the prepaid accountholder wishes to transfer funds owed (see, e.g., 118).

In some implementations, the PAFT may allow the prepaid account holder101 to invite the users 102-104 (to whom the prepaid account holderdesires to transfer funds owed), to open prepaid accounts via the PAFT.The PAFT may open prepaid accounts for such users, and may provide linksbetween the prepaid account of the prepaid account holder 101 and theuser 102-104. In some implementations, the PAFT may facilitate fast,reliable, and secure transfer of funds from the prepaid account of theprepaid account holder 101 to the prepaid accounts of the users 102-104.In some implementations, the PAFT may initiate funds transferimmediately upon opening of the prepaid accounts of the users 102-104.Thus, if the users accept the invitation of the prepaid account holder,the PAFT may, in some implementations, conduct real-time secure transferof funds from the prepaid account holder to the users. In someimplementations, the PAFT may also allow the account holders and/orusers to create transfer schedules for future funds transfers. In someimplementations, the PAFT may enable the users who received new accountsto similarly invite others who do not have prepaid accounts to establishnew prepaid accounts with the PAFT to facilitate further fundstransfers. Such prepaid account funds transfers may also allow thetransferors of funds owed to exercise spending controls for themselvesvia their prepaid accounts.

FIG. 2 shows a data flow diagram illustrating an example procedure togenerate a customized invitation for a user to open a new prepaidaccount in some embodiments of the PAFT. In some implementations, atransferor user 201 may wish to invite a transferee user 206 to open aprepaid account for funds transfer. The transferor user may utilize atransferor client 202 communicating with a PAFT server 203 (“server”) togenerate a prepaid account invitation customized for the transfereeuser. For example, the transferor user may provide user input, e.g.,invitation request input 211, into the client device. In variousimplementations, the user input may include, but not be limited to:keyboard entry, mouse clicks, depressing buttons on a joystick/gameconsole, voice commands, single/multi-touch gestures on atouch-sensitive interface, touching user interface elements on atouch-sensitive display, and/or the like.

In some implementations, the user may provide invitation request input,e.g., 211, to the transferor client indicating that the user desires toinvite the transferee user to apply for a prepaid account. For example,the transferor user may desire for the transferee user to open theprepaid account so that the transferor user can transfer funds to thetransferee user's newly opened prepaid account. As another example, thetransferor user may wish to obtain funds from the transferee user on aregular basis (e.g., according to a predetermined schedule), and maywish for the transferee user to utilize a prepaid account to provide thepayments for funds transfer for risk minimization and/or securitypurposes.

In response to the transferor providing the invitation request input,the transferor client may generate a prepaid account invitation request,e.g., 212, and provide, e.g., 213, the generated prepaid accountinvitation request to the server, e.g., 203. For example, a browserapplication executing on the transferor client may provide, on behalf ofthe user, a (Secure) Hypertext Transfer Protocol (“HTTP(S)”) POSTmessage including the prepaid account invitation request details for theserver in the form of data formatted according to the eXtensible MarkupLanguage (“XML”). Below is an example HTTP(S) POST message that may besent by a browser executing on the transferor client to provide aprepaid account invitation request to the server:

POST /inviterequests.php HTTP/1.1 Host: www.paft.com Content-Type:Application/XML Content-Length: 921 <?XML version = “1.0” encoding =“UTF-8”?> <paft_invitation_request>  <request_id>FBSWEUHY48</request_id>   <timestamp>2011-02-0909:27:13</timestamp>   <transferor_ID>transferor@paft.com</user_ID>  <client_IP>192.168.20.78</client_IP>   <transferee_details>    <transferee_type>individual</transferee_type>    <first_name>John</first_name>     <last_name>Public</last_name>    <contact_type>email</contact_type>    <contact_info>john.q.public@gmail.com</contact_info>    <alt_contact_type>SMS</alt_contact_type>    <alt_contact_info>415-927-4555</alt_contact_info>    <client_type>smartphone</client_type>   </transferee_details>  <num_invite_attempts>3</num_invite_attempts>   <account_params>    <same_bank>yes</same_bank>     <same_branch>no</same_branch>    <persistent_link>yes</persistent_link>   </account_params>  <transfer_params>     <on_schedule>no</on_schedule>    <one_time>yes</one_time>     <amount>$250.00</amount>    <instant_transfer>yes</instant_transfer>   </transfer_params></paft_invitation_request>

Upon receiving the prepaid account invitation request from thetransferor client, the server 203 may parse the invitation request toextract the included invitation request data. Parsing procedures thatthe server may employ are outlined in the description below withreference to FIG. 12. Upon determining the parameters of the invitationrequest, the server may generate a unique ID associated with theinvitation to be generated based on the request. In someimplementations, the server may extract, based on parsing the requestmessage, data regarding the messaging mode (e.g., SMS, email, voicemail,automated/manual phone call, postal mail, etc.) by which the transferoruser desires the PAFT to provide a prepaid account invitation for thetransferee user. Based on the user messaging mode preference(s), theserver may generate a query, e.g., 214, for a template from a databasewhich the server can utilize to generate a customized prepaid accountinvitation message for the transferee user in accordance with themessaging mode preferences of the transferor user. The server may issuethe query, e.g., 215, to a database storing invitation templates, e.g.,forms database 204 a. For example, the server may execute a PHP scriptincluding Structured Query Language (“SQL”) commands to query arelational database storing invitation templates. An example listing,written substantially in the form of PHP/SQL commands, illustratingsubstantive aspects of querying the database for an invitation templateis provided below:

<?PHP header(‘Content-Type: text/plain’); functioninvitation_template_query($template_type, $DBserver, $password) {mysql_connect(“254.92.185.102”,$DBserver,$password); // access databaseserver mysql_select_db(“TEMPLATES.SQL”); // select database table tosearch //create query for invitation template $query = “SELECTinvitation_template FROM TemplateStore WHERE   type LIKE ‘%’$template_type”; $result = mysql_query($query); // perform the searchquery mysql_close(“TEMPLATES.SQL”); // close database access return$result; // return search results ?>

In response to the invitation template query, the forms database mayprovide, e.g., 216, the requested invitation template to the server. Insome implementations, the server may parse, e.g., 217, the invitationrequest to determine information of the transferee user who will be therecipient of the prepaid account invitation. Based on the recipientinformation of the transferee user, the server may generate a customizedprepaid account invitation. For example, the customized prepaid accountinvitation may take the form of a text message, SMS, email, electroniccommunication, fax, voicemail, automated phone call, script print-outfor a customer service representative to make a manual phone call,automated/manual online chat script, webpage, and/or the like. In someimplementations, the server may store, e.g., 218, the generatedcustomized invitation, unique ID, and/or other invitation data to adatabase, eg., invitations database 204 b. An example listing, writtensubstantially in the form of PHP/SQL commands, to store the invitationdata to a database is provided below:

<?PHP header(‘Content-Type: text/plain’);mysql_connect(“254.92.185.103”,$DBserver,$password); // access databaseserver mysql_select(″INVITATIONS.SQL″); // select database to appendmysql_query(“INSERT INTO UserInvitationsTable (requestID,  transferorID,transferorIP, time, uniqueID, transfereetype,  transfereename,transfereecontacttype, transfereecontactinfo,  altcontactinfo,transfereeclienttype, numinvites, samebank, samebranch,  persistentlink,onschedule, onetime, amount, instanttransfer,  custominvite) VALUES($request_ID, $transferor_ID, $transferor_IP, $timestamp,  $unique_ID, $transferee_type, $transferee_name, $transferee_contact_type, $transferee_contact_info, $alt_contact_info, $transferee_client_type, $num_invite_attempts, $same_bank, $same_branch,  $persistent_link, $on_schedule, $one_time, $amount, $instant_transfer, $custom_invitation)”);  // add data to table in databasemysql_close(″INVITATIONS.SQL″); // close connection to database ?>

In some implementations, the server may provide the generated customizedprepaid account invitation, e.g., 219, for a transferee client, e.g.,205, of a transferee user, e.g., 206, specified by the invitationrequest of the transferor user. For example, the server may send anelectronic mail message to an electronic mail messaging account of thetransferee user. An example listing, written substantially in the formof PHP/SQL commands, for the server to send an electronic mail messageto an electronic mail messaging account of the transferee user isprovided below:

<?PHP header(‘Content-Type: text/plain’); // customized invitation isstored in data variable $message, and transferor   user name is storedin $transferor $to = ‘john.q.public@gmail.com’; $subject = ‘PrepaidAccount Invitation from ’ . $transferor; $headers = ‘From:invitations@paft.com’ . “\r\n” .   ‘Reply-To: invitations@paft.com’ .“\r\n” .   ‘X-Mailer: PHP/’ . phpversion( ); mail($to, $subject,$message, $headers); ?>

In some implementations, the transferee client may render, e.g., 220,the customized prepaid account invitation for presentation to thetransferee user. For example, the transferee client may render awebpage, electronic message, text/SMS message, buffer a voicemail, emita ring tone for the transferee user to answer a phone and/or play anaudio message, etc. The transferee client may then present thecustomized prepaid account invitation for the transferee user, e.g.,221. For example, the transferee client may provide output including,but not limited to: sounds, music, audio, video, images, tactilefeedback, vibration alerts (e.g., on vibration-capable client devicessuch as a smartphone etc.), and/or the like. In some implementations,the server may also provide an invitation confirmation message, e.g.,222, for the transferor client of the transferor user. For example, theserver may send an electronic mail message to an electronic mailmessaging account of the transferor user. The transferor client mayrender, e.g., 223, the customized prepaid account invitation forpresentation to the transferor user. For example, the transferee clientmay render a webpage, electronic message, text/SMS message, buffer avoicemail, emit a ring tone for the transferee user to answer a phoneand/or play an audio message, etc. The transferor client may thenpresent the customized prepaid account invitation for the transferoruser, e.g., 224. For example, the transferor client may provide outputincluding, but not limited to: sounds, music, audio, video, images,tactile feedback, vibration alerts (e.g., on vibration-capable clientdevices such as a smartphone etc.), and/or the like.

FIGS. 3A-B show logic flow diagrams illustrating example aspects ofgenerating a customized invitation for a user to open a new prepaidaccount in some embodiments of the PAFT, e.g., a Prepaid AccountApplication Invitation (PAAI) component 300. In some implementations, atransferor user may invite a transferee user to open a prepaid accountfor funds transfer. For example, the transferor user may provideinvitation request input, e.g. 301, into the transferor client. In someimplementations, the user provided invitation request input may indicateto the transferor client that the user desires to invite the transfereeuser to apply for a prepaid account. For example, the transferor usermay desire for the transferee user to open the prepaid account so thatthe transferor user can transfer funds to the transferee user's newlyopened prepaid account. As another example, the transferor user may wishto obtain funds from the transferee user on a regular basis (e.g.,according to a predetermined schedule), and may wish for the transfereeuser to utilize a prepaid account to provide the payments for fundstransfer for risk minimization and/or security purposes. In response tothe transferor providing the invitation request input, the transferorclient may generate a prepaid account invitation request, e.g., 302, andprovide the generated prepaid account invitation request to the PAFTserver.

Upon obtaining, e.g., 303, the prepaid account invitation request fromthe transferor client, the server may parse the invitation request toextract the included invitation request data, e.g., 304. Parsingprocedures that the server may employ are outlined in the descriptionbelow with reference to FIG. 12. Based on the parsing, the server mayextract data fields including, but not limited to: request_id,timestamp, transferor_id, client_IP, transferee_details_list,transferee_type, first_name, last_name, contact_type, contact_info,alt_contact_info, alt_contact_type, alt_contact_info, client_type,num_invite_attempts, account_params_list, same_bank_flag,same_branch_flag, persistent_link_flag, transfer_param_list,on_schedule_flag, one_time_flag, amount, instant_transfer_flag,custom_invitation, transferee_details_list, transferee_client_IP, and/orthe like. Upon determining the parameters of the invitation request, theserver may generate a unique ID associated with the invitation to begenerated based on the request, e.g., 306. For example, the server mayexecute a hypertext preprocess (“PHP”) script which invokes the md5( )command to generate a hash of the invitation request message, andutilize the generated message hash as the unique invitation ID. Asanother example, the server may utilize the rand( ) command to generatea random number to be utilized as the unique invitation ID. In someimplementations, the server may extract, based on parsing the requestmessage, data regarding the messaging mode (e.g., SMS, email, voicemail,automated/manual phone call, postal mail, etc.) by which the transferoruser desires the PAFT to provide a prepaid account invitation for thetransferee user. Based on the user messaging mode preference(s), theserver may generate a query, e.g., 307, for a template from a databasewhich the server can utilize to generate a customized prepaid accountinvitation message for the transferee user in accordance with themessaging mode preferences of the transferor user. The server may issuethe query to a database storing invitation templates, e.g., a formsdatabase. In response to the invitation template query, the formsdatabase may provide, e.g., 308, the invitation template to the server.

In some implementations, the server may parse, e.g., 309, the invitationrequest to determine information of the transferee user who will be therecipient of the prepaid account invitation. For example, the server mayextract data field such as, but not limited to: transferee_ID,transferee_type, first_name, last_name, contact_type, contact_info,alt_contact_info, alt_contact_type, alt_contact_info, client_type,and/or the like. Based on the recipient information of the transfereeuser, the server may generate, e.g., 310, a customized prepaid accountinvitation. For example, the customized prepaid account invitation maytake the form of a text message, SMS, email, electronic communication,fax, voicemail, automated phone call, script print-out for a customerservice representative to make a manual phone call, automated/manualonline chat script, webpage, and/or the like. In some implementations,the server may generate, e.g., 311, a customized invitation data recordincluding the data fields, unique ID, customized invitation, and/orother invitation data, and provide the invitation data record to adatabase, e.g., invitations database for storing the invitation data,e.g., 312. In some implementations, the server may provide the generatedcustomized prepaid account invitation, e.g., 313, for a transfereeclient of a transferee user specified by the invitation request of thetransferor user. In some implementations, the transferee client mayrender, e.g., 314, the customized prepaid account invitation forpresentation to the transferee user. The transferee client may thenpresent the customized prepaid account invitation for the transfereeuser, e.g., 315. In some implementations, the server may also provide aninvitation confirmation message, e.g., 316, for the transferor client ofthe transferor user. The transferor client may render, e.g., 317, thecustomized prepaid account invitation for presentation to the transferoruser. The transferor client may then present the customized prepaidaccount invitation for the transferor user, e.g., 318.

FIGS. 4A-C show data flow diagrams illustrating an example procedure toregister a new prepaid account for a user in some embodiments of thePAFT. In some implementations, the transferee user may desire to acceptthe invitation offer by the server to open a prepaid account with thePAFT. For example, the transferee user 406 may provide invitationacceptance input, e.g., 411, to the transferee client to conveyacceptance of the invitation. In various implementations, the user inputmay include, but not be limited to: keyboard entry, mouse clicks,depressing buttons on a joystick/game console, voice commands,single/multi-touch gestures on a touch-sensitive interface, touchinguser interface elements on a touch-sensitive display, and/or the like.For example, the transferee user may activate a hyperlink in an emailmessage sent by the server to the transferee user including a customizedprepaid account invitation. Activating the hyperlink may serve as thesignal for the transferee client that the transferee user wishes toaccept the customized prepaid account invitation. In response to thetransferee user input, the transferee client may generate a prepaidaccount invitation acceptance message, e.g., 412 for the server. Forexample, a browser executing on the transferee client may generate aHTTP(S) GET message including the prepaid account invitation acceptancemessage. An example HTTP(S) GET message that may be sent by a browserexecuting on the transferee client to provide a prepaid accountinvitation acceptance message to the server is provided below:

GET /inviteaccept.php HTTP/1.1 Host: www.paft.com Content-Type:Application/XML Content-Length: 894 <?XML version = “1.0” encoding =“UTF-8”?> <paft_invitation_accept> <invitation_id>VBUQQW9M,</invitation_id>  <accept_timestamp>2011-02-1008:27:13</accept_timestamp> <transferor_ID>transferor@paft.com</user_ID>  <transferee_details>    <transferee_type>individual</transferee_type>    <first_name>John</first_name>     <last_name>Public</last_name>    <contact_type>email</contact_type>    <contact_info>john.q.public@gmail.com</contact_info>    <alt_contact_type>SMS</alt_contact_type>    <alt_contact_info>415-927-4555</alt_contact_info>    <client_type>smartphone</client_type>  </transferee_details> <client_IP>192.168.20.67</client_IP>  <account_params>    <same_bank>yes</same_bank>     <same_branch>no</same_branch>    <persistent_link>yes</persistent_link>  </account_params> <transfer_params>     <on_schedule>no</on_schedule>    <one_time>yes</one_time>     <amount>$250.00</amount>    <instant_transfer>yes</instant_transfer>  </transfer_params></paft_invitation_accept>

Upon receiving the prepaid account invitation acceptance message fromthe transferee client, the server 403 may parse the invitationacceptance to extract the included invitation acceptance data, e.g.,414. For example, the server may extract the unique invitation ID of theinvitation which the transferee user has accepted. Based on theextracted invitation data, the server may, in some implementations,determine the type of invitation to which the transferee user hasresponse with acceptance and a client type of the transferee user. Inalternate implementations, the server may use the extracted invitationdata, e.g., the unique invitation ID, to query, e.g., 415, a database,e.g., invitations database 404 b, for the type of the invitation. Forexample, the server may obtain the invitation type from the database byissuing PHP/SQL commands similar to those described above with referenceto FIG. 2. In response, the database may provide the invitation type,e.g., 416, for the server.

In some implementations, the server may generate a query for a prepaidaccount application form using the invitation type and client type ofthe transferee user. For example, various transferee users and/or clientmay require and/or prefer different types of prepaid account applicationforms. For example, a prepaid account application form may be providedas a (Dynamic) HyperText Markup Language (“HTML”) page, interactiveAdobe® Flash object, iPhone® app, Android™ app, interactive voiceapplication, etc. Also, the size, resolution, fidelity and/or likeattributes of the prepaid account application form may be customizeddepending on the screen size, pixel count, audio/video processingcapabilities and/or like attributes and/or preferences of the transfereeclient and/or transferee user. Thus, the server may generate a query fora prepaid application form that is customized to the transferee clientand/or transferee user, and issue the query, e.g., 418, to a database,e.g., forms database 404 a. In response to the prepaid accountapplication form query, the database may provide a prepaid accountapplication form, e.g., 419, that is customized to the attributes and/orpreferences of the transferee client and/or transferee user. The servermay provide the obtained prepaid account application form, e.g., 420, tothe transferee client. For example, the server may provide thetransferee client with a HTML page including a reference to an Adobe®Flash object stored on the server including the prepaid accountapplication. An example HTML code listing including JavaScript™ commandsreferencing an Adobe® Flash object within the HTML page is providedbelow:

<html> <div id=“PAFT”>  If you're seeing this, you don't have FlashPlayer installed. </div> <script type=“text/javascript”>   var app = newSWFObject(“www.paft.com/prepaid_app.swf”,   “Media”, “640”, “480”, “8”,“#000000”);   app.addParam(“quality”, “high”);   app.write(“PAFT”);</script> </html>

Upon obtaining the prepaid account application, the transferee clientmay execute the prepaid account application for presentation to theuser, e.g., 422. For example, with reference to the examples above, aweb browser executing on the transferee client device may render, e.g.,421, the HTML web page and may communicate with the server to downloadthe Adobe® Flash object. An Adobe® Flash browser plug-in installed onthe transferee client and operating in conjunction with the browser mayplay/execute the downloaded Flash object for presentation, e.g., 422, tothe transferee user.

In some implementations, the transferee user may provide applicationform input, e.g., 423, to the transferee client. For example, withreference to the example above, the Adobe® Flash object including theprepaid account application may provide interactive features, and mayallow the user to enter user input/feedback, e.g. 423, via a variety ofmechanisms (e.g., keyboard entry into a command-line interface, mouseinput in a graphical user interface, gestures on a touch-sensitiveinterface, voice commands, etc.). Using the user application form input,the client may generate, e.g., 424, a completed prepaid accountapplication. For example, the transferee client executing the Adobe®Flash object may generate, maintain, update and/or store data pertainingto the user's interaction with the Adobe® Flash object (e.g., anapplication state, an application data structure, a block of memory withdata variables, etc.). For example, the Adobe® Flash object may store aprepaid account application data structure encoded according to theJavaScript Object Notation (“JSON”) format. An example JSON-encodedprepaid account application data structure is provided below:

“prepaid_account_application_data” { “timestamp”: “2010-06-30 09:23:47”,“application_id”: “A236269”, “md5_auth”:“f585e3efede0c3b400b25908f8fa3f6d”, “applicant_details”: {“applicant_id”: “jqpublic”, “applicant_name”: “John Q. Public”, “dob”:“1976-02-15”, “ssn”: “123-45-6789”, “credit_check_ok”: “yes”,“address_firstline”: “123 Green Blvd.”, “address_secondline”: “Apt 58”,“zipcode”: “98765”, “City”: “Terrace Heights”, “State”: “CA” },“account_params”: { “account_mode”: “prepaid”, “account_type”: “debit”,“account_expiry”: “none”, “bank_name”: “Chasey Bank”, “bank_branch”:“auto-assign” } }

In some implementations, the server may generate a secure communicationssession with the transferee client in order to facilitate communicationduring the prepaid account application procedure between the transfereeclient and server. As an example, the prepaid account application mayprovide data stored on the transferee client for the server as prepaidaccount application data, e.g., completed prepaid account application425. For example, an Adobe® Flash object running on the transfereeclient may include ActionScript™ 3.0 commands to create a Secure SocketsLayer (“SSL”) connection with a server, generate a message including aJSON-encoded data structure such as illustrated in the example above,and send the message via the secure SSL connection to the server.Example commands, written substantially in the form of ActionScript™3.0, to create a secure SSL connection to a server, load prepaid accountapplication data from a locally stored JSON-encoded data file, and senda message including the JSON-encoded data via the SSL connection to theserver, are provided below:

// import required packages import flash.events.*; importflash.net.socket; import flash.net.URLLoader; importflash.net.URLRequest; import com.adobe.serialization.json.*; // obtainserver socket policy file, create socket connection to server portsystem.security.loadPolicyFile(“xmlsocket://www.aliserver.com:208”); msg= new socket( ); msg.connect(“https://www.paft.com”, 255); // load dataas text string from .json file var loader:URLLoader = new URLLoader( );var request:URLRequst = new URLRequest( ); request.URL =“application_data.json”; loader.dataformat = “text” loader.load(request)// transmit data to server via secure SSL connection, then close socketmsg.writeMultiByte(loader.data, “UTF-8”); msg.close( );

In some implementations, the server may be executing a PHP scriptimplementing a SSL socket server which listens to incomingcommunications on a server port to which the transferee client may senddata, e.g., prepaid account application 425, encoded according to theJSON format. Upon identifying an incoming communication, the PHP scriptmay read the incoming data from the transferee client into a memoryvariable which can then be operated upon by the transferee client. Anexample listing, written substantially in the form of PHP/SQL commands,to accept JSON-encoded prepaid account application data from atransferee client via a SSL connection is provided below:

<?PHP header(‘Content-Type: text/plain’); // set ip address and port tolisten to for incoming data $address = ‘192.168.0.100’; $port = 255; //create a server-side SSL socket, listen for/accept incomingcommunication $sock = socket_create(AF_INET, SOCK_STREAM, 0);socket_bind($sock, $address, $port) or die(‘Could not bind to address’);socket_listen($sock); $client = socket_accept($sock); // read input datafrom client in 1024 byte blocks until end of message do {  $input = “”; $input = socket_read($client, 1024);  $data .= $input; } while($input!= “”); ?>

In some implementations, the server may parse the obtained completedprepaid account application form from the transferee client, and extractthe application data from the completed prepaid account applicationform. Based on the application data, the server may generate anapplication screening request, e.g., 426. In some implementations, theserver may generate a request to perform a security and/or credit checkon the applicant. For example, the server may generate an applicantscreening request, e.g., 427, for a credit check service such asEquifax®. In such an example, the server may provide a HTTP(S) POSTmessage to a screening server, e.g., 407, including applicant detailsextracted from the completed prepaid account application. An exampleHTTP(S) POST message including an applicant screening request that maybe sent by the PAFT server to a screening server is provided below:

POST /applicantscreen.php HTTP/1.1 Host: www.screeningserver.comContent-Type: Application/XML Content-Length: 1151 <?XML version = “1.0”encoding = “UTF-8”?> <request>  <request_headerinterface_version_no=″1.0″ dtd_version_no=″1.0″>    <client_reference>A236269</client_reference>  </request_header> <service_request id=″201102091121″>  <consumer_bureau_service> <consumer_bureau_request domain=″***″ usercode=″***″  password=″***″operator_id=″0000-0044″>  <consumer_search search_type=″SE″opt_in_out_flag=″I″  associate_jointapp_flag=″″>  <scoringqcb_option=″1″ same_company_insight=″″>     <score_productcode=″RNISF02″/>  </scoring >  <data_types>     <data_type id=″ADO″maximum=″00″ />     <data_type maximum=″00″ />     <data_type id=″CJR″maximum=″00″ />     <data_type maximum=″00″ />     <data_typemaximum=″00″ />     <data_type maximum=″00″ />     <data_typemaximum=″00″ />     <data_type maximum=″00″ />  </data_types> <display_requirements applicant_data=″Y″ associate_data=″Y″ attributable_data=″N″ potential_associate_data=″N″  family_data=″N″ /> <applicant_details title=″″ forename=″John″ second_name=″Q.″ surname=″Public″>  <address_details time_at_address=″″address_match_flag=″″  address=″123 Green Blvd. Apt 58, Terrace HeightsCA 98765″>  </address_details>  </applicant_details>  </consumer_search> </consumer_bureau_request>  </consumer_bureau_service> </service_request> </request>

Upon receiving the applicant screening request, the screening server mayprocess the applicant screening request, and may generate an applicantscreening report. For example, the screening server may determine thatthe applicant fails the screening tests for obtaining a prepaid accountwith the PAFT. In such an example, the screening server may provide anapplicant screening failure report, e.g., 428 a. If the screening serverdetermines that the applicant passed the screening tests for obtaining aprepaid account with the PAFT, the screening server may respond to theapplicant screening request with an applicant screening success report,e.g., 428 b. For example, the screening server may provide a HTTP(S)POST message to a PAFT server including an applicant screening reportindicating success or failure on the part of the applicant to pass thescreening tests. An example HTTP(S) POST message including an applicantscreening report is provided below:

POST /screenresults.php HTTP/1.1 Host: www.paft.com Content-Type:Application/XML Content-Length: 1151 <?XML version = “1.0” encoding =“UTF-8”?> <response>  <response_header>     <client_reference>A236269</client_reference>  </response_header>  <service_responseid=“201102091121” success_flag=“1”>  <consumer_bureau_service> <consumer_bureau_response>  <header error_code=“00” error_message=“”reference=“”/>  <non_address>     <supplied_address id=“ADS”sequence_number=“1” noc_indicator=“N”/>     <score id=“SCO”label=“RNISF02” sign=“+” score=“528”/>  </non_address>  <address_detailssequence_number=“1” match_indicator=“L”>  <address_matched id=“ADO”address_key=“58150004076” house_name=“”  house_number=“123”street_1=“GREEN BLVD” street_2=“Apt 58” district=“”  posttown=“TERRACEHEIGHTS” county=“LOS LOBOS” postcode=“98765”  address_type=“HOME”/> <electoral_roll id=“ELR” name_match_indicator=“A” title=“”forename=“John”  second_name=“Q” surname=“Public” date_of_birth=“”period=“07-10”  junior_senior=“”/>  <insight id=“INR”name_match_indicator=“C” title=“MR.” forename=“John”  second_name=“Q”surname=“PUBLIC” date_of_birth=“YYYY-MM-DD”  company_class=“FN”account_type=“03” account_number=“” start_date=“2005-03-  01”end_date=“2006-11-12” update_date=“2011-02-09” credit_limit=“0” current_balance_sign=“+” current_balance=“0” start_balance=“0” default_balance=“0” credit_terms=“275” repayment_period=“300” payment_frequency=“M” payment_history=“S” delinquent_date=“” client_number=“” quality_flags=“” quality_indicator_1=“” quality_indicator_2=“” credit_card_payment_amount_sign=“” credit_card_payment_amount=“”credit_card_previous_statement_balance_sign=“” credit_card_previous_statement_balance=“”credit_card_cash_advance_value=“”  credit_card_cash_advance_count=“”credit_card_limit_change_flag=“”  credit_card_minimum_payment_flag=“”credit_card_promotional_rate_flag=“”/>  </address_details> </consumer_bureau_response>  </consumer_bureau_service> </service_response> </response>

Upon receiving the applicant screening report, the PAFT server maydetermine whether the transferee user applicant passed the screeningtests. If the applicant failed the screening tests, the server maygenerate an application denial notification, e.g., 429 a. For example,the server may generate a HTTP(S) POST message similar to the exampledescribed above. The server may provide the application denialnotification to the transferee client, and the transferee client mayrender, e.g., 430 a, and display, e.g., 431 a, the application denialnotification for the transferee user.

In some implementations, the server may determine that the transfereeuser applicant passed the screening tests performed by the screeningserver based on parsing the applicant screening report. In suchimplementations, the server may proceed with creation of a new prepaidaccount for the transferee user. For example, the server may determinewhether the new prepaid account can be hosted locally, of if the prepaidaccount should be hosted at a different bank/branch/server. For example,the server may obtain the prepaid account preferences from thetransferor user's prepaid account application invitation request and/orfrom the transferee user's completed prepaid application. If the newprepaid account can be hosted locally, the server may generate a newuser profile and/or user account database record(s) reflecting a newprepaid account for the transferee user, e.g., 429 b. If the prepaidaccount is required to be hosted on another server, e.g., bank/branchserver 408, the PAFT server may generate a prepaid account openingrequest message, e.g., 430 b, for the bank/branch server. For example,the PAFT server may generate a HTTP(S) GET message including a prepaidaccount opening request message, similar to the example provided below:

GET /newaccountrequest.php HTTP/1.1 Host: www.bankbranch.comContent-Type: Application/XML Content-Length: 894 <?XML version = “1.0”encoding = “UTF-8”?>  <new_account_request> <request_id>VBUQQW9M,</request_id>  <request_timestamp>2011-02-1008:27:13</request_timestamp>  <requestor_ID>manager@paft.com fortransferee@paft.com  </requestor_ID>  <account_details>     <account_holder>individual</account_holder>     <account_type>prepaid debit</account_type>     <first_name>John</first_name>      <last_name>Public</last_name>     <contact_type>email</contact_type>     <contact_info>john.q.public@gmail.com</contact_info>     <opening_balance>$250.00</opening_balance>  </account_details></new_account_request>

In some implementations, the bank/branch server may require additionalinformation on the transferee user, invitation request, and/or the like,and may request additional user information, e.g., additional userinformation request 432. For example, the bank/branch server may provideto the PAFT server a HTTP(S) POST message similar to the examples above.The PAFT server may parse any obtained additional user informationrequest(s), and obtain from local storage, database(s) and/or anyPAFT-affiliated entities and/or components the additional informationrequested, e.g., 433. The PAFT server may in response generate, e.g.,434, an additional user information message, for example, in the form ofa HTTP(S) POST message similar to the examples above, and provide themessage to the bank/branch server. In some implementations, thebank/branch server may create a new prepaid account for the transfereeuser based on the information provided by the PAFT server, e.g., 435.The bank/branch server may provide an account issue message, e.g., 436,to notify the PAFT server and/or other PAFT entities and/or componentsthat a prepaid account has been created at the bank/branch server forthe transferee user.

In some implementations, the PAFT server may, upon creating the prepaidaccount for the transferee server (e.g., locally, or at another serversuch as the bank/branch server), generate a prepaid account link datarecord that provides a link between the prepaid accounts of thetransferor and transferee user. The server may also generate, e.g., 437a transfer schedule that may specify funds transfer attributes betweenthe transferor and transferee prepaid accounts, such attributesincluding, but not limited to: number of transfers, transfer dates,transfer frequency, transfer intervals, transfer amounts, transfernotification settings, and/or the like. An example transfer scheduleencoded according to the XML format is provided below:

<?XML version = “1.0” encoding = “UTF-8”?> <transfer_schedule> <timestamp>2011-02-10 08:27:15</timestamp> <transferor_ID>transferor@paft.com</transferor_ID> <transferee_ID>transferee@paft.com</transferee_ID> <link_ID>45UIVBNYT9</link_ID>  <num_transfers>6</num_transfers> <transfer_date>01 of mo</transfer_date>  <transfer_frequency>1 per 2mo</transfer_frequency>  <transfer_interval>2 mo</transfer_interval> <notify_settings>transferor transferee</notify_settings></transfer_schedule>

In some implementations, the server may store a user profile record,e.g., 438, prepaid account link data record, e.g., 439, and prepaidaccount funds transfer schedule record, e.g., 440, to database(s), e.g.,users database 404 c, links database 404 d, and schedules database 404e. For example, the server may issue PHP/SQL commands similar to theexample below to store the user profile, prepaid account link data, andprepaid account funds transfer schedule records in database(s):

<?PHP header(‘Content-Type: text/plain’);mysql_connect(“254.92.185.103”,$DBserver,$password); // access databaseserver // write user profile data into users databasemysql_select(“USERS.SQL”); // select database to appendmysql_query(“INSERT INTO UserTable (timestamp, userID, clientIP,usertype,  firstname, lastname, contacttype, contactinfo,altcontactinfo,  clienttype,ssn, dob, creditreport, accountnumbers)VALUES (time( ), $user_ID, $client_IP, $user_type, $first_name,$last_name,  $contact_type, $contact_info, $alt_contact_info,$client_type,$ssn, $dob,  $credit_report, $account_num_list)”); // adddata to table in database mysql_close(“USERS.SQL”); // close connectionto database // write prepaid account link data into link databasemysql_select(“LINKS.SQL”); // select database to appendmysql_query(“INSERT INTO LinkTable (timestamp, link_ID,bidirectional_flag,  transferor_ID, transferor_account_num,transferor_bank, transferor_branch,  transferor_ABA, transferee_ID,transferee_account_num, transferee_bank,  transferee_branch,transferee_ABA) VALUES (time( ), $link_ID, $bi_flag, $transferor_ID,$transferor_account_num,  $transferor_bank, $transferor_branch,$transferor_ABA, $transferee_ID,  $transferee_account_num,$transferee_bank, $transferee_branch,  $transferee_ABA”); // add data totable in database mysql_close(“LINKS.SQL”); // close connection todatabase // write prepaid account funds transfer schedule data intoschedules database mysql_select(“SCHEDULES.SQL”); // select database toappend mysql_query(“INSERT INTO ScheduleTable (timestamp, userID,schedule_data) VALUES (time( ), $transferor_ID,$transfer_schedule_xml)”); // add data to table  in databasemysql_close(“SCHEDULES.SQL”); // close connection to database ?>

In some implementations, the server may provide an account issuenotification, e.g., 441, for the transferee (and/or transferor) user(s).For example, the server may provide a HTTP(S) POST message similar tothe examples above. The client(s) may render, e.g., 442, the accountissue notification for presentation to the user(s). For example, theclient(s) may render a webpage, electronic message, text/SMS message,buffer a voicemail, emit a ring tone for the user(s) to answer a phoneand/or play an audio message, etc. The client(s) may then present theaccount issue notification for the user(s), e.g., 443. For example, theclient(s) may provide output including, but not limited to: sounds,music, audio, video, images, tactile feedback, vibration alerts (e.g.,on vibration-capable client devices such as a smartphone etc.), and/orthe like.

FIGS. 5A-D show logic flow diagrams illustrating example aspects ofregistering a new prepaid account for a user in some embodiments of thePAFT, e.g., a Prepaid Account Registration (PAR) component 500. In someimplementations, the transferee user may desire to accept the invitationoffer by the server to open a prepaid account with the PAFT. Forexample, the transferee user may provide invitation acceptance input,e.g., 501, to the transferee client to convey acceptance of theinvitation. In response to the transferee user input, the transfereeclient may generate a prepaid account invitation acceptance message,e.g., 502, for the PAFT server. Upon obtaining, e.g., 503, the prepaidaccount invitation acceptance message from the transferee client, theserver may parse the invitation acceptance to extract the includedinvitation acceptance data, e.g., 504. For example, the server mayextract data fields including, but not limited to: request_id,timestamp, transferor_id, client_IP, transferee_type, first_name,last_name, contact_type, contact_info, client_type, account_params_list,same_bank_flag, same_branch_flag, persistent_link_flag,transfer_param_list, on_schedule_flag, one_time_flag, amount,instant_transfer_flag, custom_invitation, transferee_details_list,transferee_client_IP, client_type, client_MAC, client_IP,presentation_format, pixel_count, resolution, screen_size,audio_fidelity, hardware_settings_list, software_compatibilities_list,installed_apps_list, and/or the like. Based on the extracted datafields, the server may determine the type of transferee client, e.g.,505. For example, the server may determine whether the transferee clientis a desktop computer, tablet computer, mobile phone accessing email,text voice messages, etc. For example, the server may determine theattributes of the client device such as the screen resolution, screensize, audio/video capabilities, hardware configuration, softwareconfiguration, applications installed on the client, and/or the like.The server may also extract the unique ID of the invitation from theinvitation acceptance, e.g., 506. Based on the extracted invitationdata, the server may, in some implementations, generate a query for thetype of the invitation, e.g., 507, and provide the query to a database,e.g., an invitations database. For example, the server may query forinvitation attributes such as, but not limited to: transferee_type,account_params_list, account_mode, account_type, account_expiry,preferred_bank, preferred_branch, and/or the like. For example, usingsuch data fields server may determine such details as whether theinvitation is for an individual/merchant for opening of a credit/debitaccount, whether the account is prepaid/savings/checking/money marketaccount etc. In response to the server's query, the database may providethe requested information, e.g., 508.

In some implementations, the server may generate a query for a prepaidaccount application form using the invitation type and client type ofthe transferee user. The server may generate a query for a prepaidapplication form, e.g., 509, that is customized to the transferee clientand/or transferee user, and issue the query to a database, e.g., a formsdatabase. In response to the prepaid account application form query, thedatabase may provide a prepaid account application form, e.g., 510, thatis customized to the attributes and/or preferences of the transfereeclient and/or transferee user. The server may provide the obtainedprepaid account application form, e.g., 511, to the transferee client.Upon obtaining the prepaid account application, the transferee clientmay render/execute, e.g, 512, the prepaid account application, andpresent the prepaid account application for the transferee user, e.g.,513.

In some implementations, the transferee user may provide applicationform input, e.g., 514, to the transferee client. Using the userapplication form input, the client may generate, e.g., 515, a completedprepaid account application. The transferee client may provide thecompleted prepaid account application for the server. In someimplementations, the server may obtain the completed prepaid accountapplication form from the transferee client, e.g., 516, and parse, e.g.,517, the completed application to extract the application data from thecompleted prepaid account application form. For example, the server mayobtain fields such as, but not limited to: applicant_ID,applicant_firstname, applicant_lastname, dob, ssn, credit_check_ok_flag,address_line1, address_line2, zipcode, city, state, account_params_list,account_mode, account_type, account_expiry, bank_name, branch_name,and/or the like. Based on the application data, the server may generatean application screening request, e.g., 518. In some implementations,the server may generate a request to perform a security and/or creditcheck on the applicant. Upon receiving the applicant screening request,e.g., 519, the screening server may process, e.g., 520, the applicantscreening request, and may generate an applicant screening report, e.g.,521. For example, the screening server may determine whether theapplicant passes or fails the screening tests for obtaining a prepaidaccount with the PAFT. Upon obtaining and parsing, e.g., 522, theapplicant screening report, the PAFT server may determine whether thetransferee user applicant passed the screening tests, e.g., 523. If theapplicant failed the screening tests, e.g., 523, option “No,” the servermay generate an application denial notification, e.g., 543. The servermay provide the application denial notification to the transfereeclient, and the transferee client may render, e.g., 545, and display,e.g., 546, the application denial notification for the transferee user.

In some implementations, the server may determine that the transfereeuser applicant passed the screening tests performed by the screeningserver based on parsing the applicant screening report, e.g., 523,option “Yes.” In such implementations, the server may proceed withcreation of a new prepaid account for the transferee user. The servermay generate a user profile for the transferee user applicant, e.g.,524. The server may also determine whether the new prepaid account canbe hosted locally, of if the prepaid account should be hosted at adifferent bank/branch/server, e.g., 525. For example, the server mayobtain the prepaid account preferences from the transferor user'sprepaid account application invitation request and/or from thetransferee user's completed prepaid application. If the new prepaidaccount can be hosted locally, e.g., 525, option “No,” the server maygenerate a new user profile and/or user account database record(s)reflecting a new prepaid account for the transferee user, e.g., 526. Ifthe prepaid account is required to be hosted on another server, e.g.,525, option “Yes,” the PAFT server may generate a prepaid accountopening request message, e.g., 527, for the bank/branch server. The PAFTserver may provide the prepaid account opening request message to thebank/branch server where the account should be opened, based on theapplicant data extracted from the applicant's completed prepaid accountapplication form. In some implementations, the bank/branch server may,upon obtaining the prepaid account opening request, e.g., 528, parse theprepaid account opening request, e.g., 529, and extract request data.For example, the bank/branch server may extract fields including, butnot limited to: applicant_firstname, applicant_lastname,applicant_address_line1, applicant_address_line2, applicant_clear_flag,and/or the like. If the bank/branch server determines that it requiresadditional information, e.g., 530, for example on the transferee user,invitation request, and/or the like, the bank/branch server may generatean additional user information request, e.g., 531, and provide therequest for additional user information to the PAFT server. The PAFTserver may parse, e.g., 532, the additional user information requestfrom the bank/branch server, and determine the additional userinformation requested, e.g., 533. The PAFT server may generate anadditional user information message, e.g., 534, using, for example,information obtained from local storage, database(s) and/or anyPAFT-affiliated entities and/or components. The PAFT server may providethe message to the bank/branch server. Upon obtaining the additionaluser information message, e.g., 535, the bank/branch server may, in someimplementations, create a new prepaid account for the transferee userbased on the information provided by the PAFT server, e.g., 536. Thebank/branch server may generate an account issue message, e.g., 537, andprovide the account issue message to notify the PAFT server and/or otherPAFT entities and/or components that a prepaid account has been createdat the bank/branch server for the transferee user.

In some implementations, the PAFT server may, upon obtainingnotification (and/or creating) the prepaid account for the transfereeserver (e.g., locally, or at another server such as the bank/branchserver), generate a prepaid account link data record that provides alink between the prepaid accounts of the transferor and transferee user,e.g., 538. The server may also generate, e.g., 539, a prepaid accountfunds transfer schedule that may specify funds transfer attributesbetween the transferor and transferee prepaid accounts, such attributesincluding, but not limited to: number of transfers, transfer dates,transfer frequency, transfer intervals, transfer amounts, transfernotification settings, and/or the like. In some implementations, theserver may also generate a user profile record, e.g., 540. The servermay provide the user account data record, prepaid account link datarecord, and/or prepaid account funds transfer schedule record todatabase(s), e.g., users database, links database, and/or schedulesdatabase. In some implementations, the server may provide an accountissue notification, e.g., 543, for the transferee (and/or transferor)user(s). The client(s) may render, e.g., 545, the account issuenotification for presentation to the user(s). The client(s) may thenpresent the account issue notification for the user(s), e.g., 546.

FIGS. 6A-B show data flow diagrams illustrating an example procedure totransfer funds from a prepaid account of a user to a prepaid account ofanother user in some embodiments of the PAFT. In some implementations,various inputs into a server, e.g. PAFT server 603, may trigger aprepaid account funds transfer from a transferor user's prepaid accountto a transferee user's prepaid account.

As an example, the server may spontaneously initiate a prepaid accountsfunds transfer upon creation of a new prepaid account (e.g., atransferor and/or transferee user account) by the PAFT and/or affiliatedentities and/or components.

As another example, a transferor user, e.g., 601, may provide a paymentorder input, e.g., 611 a, into a transferor client, e.g., 602,requesting that funds be transferred from the transferor user's prepaidaccount into the transferee user's prepaid account. The transferorclient, may utilize the transferor user's payment order input togenerate a prepaid account payment order, e.g., 612 a. The transferorclient may provide the prepaid account payment order, e.g., 613 a, tothe server, e.g., 603, which may trigger the server to execute transferof funds as requested by the transferor user.

As another example, a transferee user, e.g., 606, may provide areceivables request input, e.g., 611 b, into a transferee client, e.g.,605, requesting that funds owed be transferred from the transferoruser's prepaid account into the transferee user's prepaid account. Thetransferee client may utilize the transferee user's receivables requestinput to generate a prepaid account receivables request, e.g., 612 b.The transferee client may provide the prepaid account receivablesrequest, e.g., 613 b, to the server, e.g., 603, which may trigger theserver to execute transfer of funds as requested by the transferee user.

As another example, the server, e.g., 603, may query a database, e.g.,schedules database 604 e, for a transfer schedule, e.g., 611 c. Forexample, the server may query the database on a continuous,periodically, on-demand, on-trigger and/or like basis. In response tothe query, the database may provide a transfer schedule, e.g., 612 c.The server may obtain the transfer schedule, and parse it to extractschedule data pertaining to transfers between the transferor user, e.g.,601, and the transferee user, e.g., 606. The server may analyze thedata, e.g., 613 c, to determine whether a transfer should be initiatedbetween the prepaid account of the transferor user and the prepaidaccount of the transferee user.

In general, it is contemplated that a variety of events and/or changesin data at any of the PAFT components and/or affiliated entities maytrigger the PAFT to perform prepaid account funds transfer from atransferor user's prepaid account to a transferee user's prepaidaccount.

In some implementations, the PAFT server may obtain a trigger, such asthose described above, to perform prepaid account funds transfer from atransferor user's prepaid account to a transferee user's prepaidaccount. In response to the trigger, the server may generate a query fora link data record, and provide the query, e.g., 614, to a database,e.g., links database 604 d. For example, the server may issue PHP/SQLcommands similar to the example provided below:

<?PHP header(‘Content-Type: text/plain’); functionlink_data_query($template_type, $DBserver, $password) {mysql_connect(“254.92.185.102”,$DBserver,$password); // access databaseserver mysql_select_db(“LINKS.SQL”); // select database table to search//create query for invitation template $query = “SELECT link_ID,bidirectional_flag, transferor_ID,  transferor_account_num,transferor_bank, transferor_branch, transferor_ABA,  transferee_ID,transferee_account_num, transferee_bank, transferee_branch, transferee_ABA FROM LinksTable WHERE transferor_ID LIKE ‘%’ $transferorAND  transferee_ID LIKE ‘%’ $transferee”; $result = mysql_query($query);// perform the search query mysql_close(“LINKS.SQL”); // close databaseaccess return $result; // return search results ?>

The database may provide the transfer link data record, e.g., 615, inresponse to obtaining the query from the server. In someimplementations, the server may generate a query for one or more userprofile data records (e.g., the user profile data records of thetransferor user and/or transferee user). The server may provide the userprofile data query, e.g., 616, to a database, e.g., users database 604c. For example, the server may issue PHP/SQL commands similar to theexample above to the users database. In response to the query, the usersdatabase may provide the requested user profile data records.

In some implementations, using the link data record and/or the userprofile data records, the server may initiate transfer for funds fromthe prepaid account of the transferor user to the prepaid account of thetransferee user. For example, the server may determine whether theprepaid accounts of the transferor user and the transferee user are bothstored locally. If the prepaid accounts are both stored locally, theserver may debit the prepaid account of the transferor user, and creditthe prepaid account of the transferee user, e.g., 618. Alternatively, inanother example, if a prepaid account of the transferor user and/ortransferee user is not stored locally, the server may generate one ormore transaction request messages using the link data and/or userprofile data, and provide the transaction request messages, e.g., 619,to one or more bank/branch servers, e.g., 608. For example, the servermay provide a HTTP(S) POST message for the bank/branch server similar tothe example provided below:

POST /transfers.php HTTP/1.1 Host: www.bankbranch.com Content-Type:Application/XML Content-Length: 569 <?XML version = “1.0” encoding =“UTF-8”?> <account_transfer_request>  <request_id>VQ358GFBE</request_id> <originator>manager@paft.com</orignator> <auth>A1834597QG26ABF49T</auth>  <timestamp>2011-02-0910:27:13</timestamp>  <action_type>debit</action_type> <action_amount>$250.00</action_amount>  <account_details>    <user_ID>transferor@paft.com</user_ID>    <user_type>individual</user_type>     <first_name>John</first_name>    <last_name>Public</last_name>    <account_num>9087612345</account_num>     <bank>Chasing Bank</bank>    <branch>455</branch>     <ABA>12399876</ABA>  </account_details></account_transfer_request>

In response, the bank/branch server may process the transaction request,e.g., 620, and provide a transaction completion message, e.g., 621, forthe PAFT server. Upon obtaining the transaction completion message(s)for the bank/branch server(s) involved in the prepaid account fundstransfer, the PAFT server may generate transaction notificationmessage(s), and provide the transaction notification message(s), e.g.,623 a-b, to the transferor client and/or transferee client. For example,the server may provide a HTTP(S) POST message similar to the examplesabove. The client(s) may render, e.g., 442, the transaction notificationmessage(s) for presentation to the user(s). For example, the client(s)may render a webpage, electronic message, text/SMS message, buffer avoicemail, emit a ring tone for the user(s) to answer a phone and/orplay an audio message, etc. The client(s) may then present thetransaction notification message(s) for the user(s), e.g., 443. Forexample, the client(s) may provide output including, but not limited to:sounds, music, audio, video, images, tactile feedback, vibration alerts(e.g., on vibration-capable client devices such as a smartphone etc.),and/or the like.

FIG. 7 shows a logic flow diagram illustrating example aspects ofimplementing a transferor user-initiated trigger for prepaid accountfunds transfer in some embodiments of the PAFT, e.g., aTransferor-Initiated Funds Transfer Trigger (Tr-FTT) component 700. Insome implementations, a transferor user may provide payment order input,e.g., 701, into a transferor client. In response, the transferor clientmay generate a prepaid account payment order, e.g., 702. The transferorclient may provide the generated prepaid account payment order to thePAFT server. In some implementations, the server may, upon obtaining theorder, e.g., 703, parse the obtained prepaid account payment order,e.g., 704. The server may extract the details of the prepaid accountpayment order, and determine, e.g., 705, whether funds should betransferred from a prepaid account of the transferor user to the prepaidaccount of the transferee user, based on the details provided in theprepaid account transfer order. For example, server may perform securitychecks to ensure that the order is issued by an authorized entity, thatthe amount of the transfer passes fraud checks, and/or the like. Theserver may also determine whether the account information, amountinformation, etc. are provided properly in the prepaid account transferorder. If the server determines that the prepaid account funds transfermust be performed, e.g., 706, option “Yes,” the server may generate aprepaid account funds transfer trigger, e.g., 710. In someimplementations, the server may push the generated prepaid account fundstransfer trigger to a queue of prepaid account funds transfer triggers.In some implementations, the server may determine that the prepaidaccount funds transfer should not take place, e.g., 706, option “No.”The server may, in such implementations, generate a payment order cancelnotice, e.g., 707, and provide the generated payment order cancel noticefor the transferor client. The transferor client may render the obtainedpayment order cancel notice, e.g., 708, and provide the rendered paymentorder cancel notice for the transferor user, e.g., 709. For example, theclient(s) may provide output including, but not limited to: sounds,music, audio, video, images, tactile feedback, vibration alerts (e.g.,on vibration-capable client devices such as a smartphone etc.), and/orthe like.

FIG. 8 shows a logic flow diagram illustrating example aspects ofimplementing a transferee user-initiated trigger for prepaid accountfunds transfer in some embodiments of the PAFT, e.g., aTransferee-Initiated Funds Transfer Trigger (Te-FTT) component 800. Insome implementations, a transferee user may provide receivables requestinput, e.g., 801, into a transferee client. In response, the transfereeclient may generate a prepaid account receivables request, e.g., 802.The transferee client may provide the generated prepaid accountreceivables request to the PAFT server. In some implementations, theserver may, upon obtaining the prepaid account receivables request,e.g., 803, parse the obtained prepaid account receivables request, e.g.,804. The server may extract the details of the prepaid accountreceivables request, and determine, e.g., 805, whether funds should betransferred from a prepaid account of the transferor user to the prepaidaccount of the transferee user, based on the details provided in theprepaid account receivables request. For example, server may performsecurity checks to ensure that the order is issued by an authorizedentity, that the amount of the transfer passes fraud checks, and/or thelike. The server may also determine whether the account information,amount information, etc. are provided properly in the prepaid accountreceivables request. If the server determines that the prepaid accountfunds transfer must be performed, e.g., 806, option “Yes,” the servermay generate a prepaid account funds transfer trigger, e.g., 810. Insome implementations, the server may push the generated prepaid accountfunds transfer trigger to a queue of prepaid account funds transfertriggers. In some implementations, the server may determine that theprepaid account funds transfer should not take place, e.g., 806, option“No.” The server may, in such implementations, generate an accountreceivables rejection notice, e.g., 807, and provide the generatedaccount receivables rejection notice for the transferee client. Thetransferee client may render the obtained account receivables rejectionnotice, e.g., 808, and provide the rendered account receivablesrejection notice for the transferee user, e.g., 809. For example, theclient(s) may provide output including, but not limited to: sounds,music, audio, video, images, tactile feedback, vibration alerts (e.g.,on vibration-capable client devices such as a smartphone etc.), and/orthe like.

FIG. 9 shows a logic flow diagram illustrating example aspects ofimplementing a server-initiated trigger for prepaid account fundstransfer in some embodiments of the PAFT, e.g., a Server-Initiated FundsTransfer Trigger (S-FTT) component 900. In some implementations, thePAFT server may generate, e.g., 901, a request for a transfer schedulefor specified transferor and transferee user(s), and may provide therequest for a database, e.g., schedules database. For example, theserver may query the database on a continuous, periodically, on-demand,on-trigger and/or like basis. In response to the request, the databasemay provide the requested transfer schedule, e.g., 902. The server mayobtain the transfer schedule, e.g., 903, and parse it to extractschedule data pertaining to transfers between the transferor user(s) andtransferee user(s), e.g., 904. The server may analyze the data, e.g.,905, to determine whether a transfer should be initiated between theprepaid account of the transferor user and the prepaid account of thetransferee user. If the server determines that a transfer should beinitiated between the prepaid account of the transferor user and prepaidaccount of the transferee user, e.g., 906, option “Yes,” the server maygenerate a prepaid account funds transfer trigger, e.g., 907. If,however, the server determines that a transfer should not be initiatedbetween the prepaid account of the transferor user and prepaid accountof the transferee user, e.g., option 906, option “No,” the server mayreset the procedure, and repeat the procedure if necessary.

FIGS. 10A-C show logic flow diagrams illustrating example aspects oftransferring funds from a prepaid account of a user to a prepaid accountof another user in some embodiments of the PAFT, e.g., a Prepaid AccountFunds Transfer Processing (PA-FTP) component 1000. In someimplementations, the PAFT server may obtain a prepaid account fundstransfer trigger, e.g., 1001, to transfer funds between a transferorprepaid user account and a transferee prepaid user account. For example,the server may obtain the trigger from a queue of prepaid account fundstransfer triggers, from a Tr-FTT component, e.g., 700, a Te-FTTcomponent, e.g., 800, a S-FTT component, e.g., 900, and/or the like PAFTentity and/or component. Upon obtaining the prepaid account fundstransfer trigger, the server may determine an amount of the funds to betransferred from the prepaid account of the transferor user to theprepaid account of the transferee user, e.g., 1002. For example, theserver may parse a payment order, a receivables request, a transferschedule, and/or the like data records to obtain an amount of funds tobe transferred. Upon determining the transfer amount, the server maygenerate a transfer link query for link data pertaining to a linkbetween the prepaid accounts of the transferor user and the transfereeuser, e.g., 1003. The server may provide the transfer link query to adatabase, e.g., a links database. In response, the database may providethe requested link data, e.g., 1004. In some implementations, the servermay generate a query for user profile data of the transferor and/ortransferee user(s), e.g., 1005. The server may issue the user profiledata queries to a database, e.g., a users database. In response toreceiving the user profile data queries, the database may provide therequested user profile data, e.g., 1006. Upon obtaining the link dataand/or the user data from the database(s), the server may determinewhether the prepaid accounts of the transferor and transferee users arestored locally, e.g., 1007.

If the server determines that both prepaid accounts are stored locally,e.g., 1008, option “Yes,” the server may debit the prepaid account ofthe transferor user by the determined amount of the prepaid accountfunds transfer, and credit the prepaid account of the transferee user bythe determined amount of the prepaid account funds transfer, e.g., 1009.In some implementations, the server may determine that both prepaidaccounts are not stored locally, e.g., 1008, option “No.” The servermay, in such implementations, generate one or more transaction requestmessage(s) to perform prepaid account actions (e.g., credit and/ordebit). The server may provide the transaction request message(s) to oneor more bank/branch servers. The bank/branch server, upon obtaining thetransaction request message, e.g., 1011, may perform the transactionaccording to the request message, e.g., 1012. The bank/branch server maygenerate a transaction completion message, e.g., 1013, and provide thetransaction completion message to the PAFT server.

In some implementations, the PAFT server may obtain an indication thatfunds transfer has been successfully completed between the prepaidaccounts of the transferor user and transferee user. If the serverdetermines that the funds transfer was successful, e.g., 1014, option“Yes,” the server may generate a funds transfer notification message forthe transferor and/or transferee user, e.g., 1016. If the serverdetermines that the funds transfer was not successful, e.g., 1014,option “No,” the server may generate a funds transfer failurenotification message for the transferor and/or transferee user, e.g.,1015. The server may provide the generated notifications for thetransferor and/or transferee clients. The client may render, e.g., 1017,the notifications, and present, e.g., 1018, the notifications for theusers. In some implementations, the server may generate, e.g., 1019,updated transaction data, user profile data, and/or schedule datarecords based on the prepaid account funds transfer (or failurethereof), and provide the data records to database(s). The database(s),e.g., schedules database(s) and/or users database(s), may store, e.g.,1020, the data records provided by the server.

FIG. 11 shows a user interface diagram illustrating example aspects ofmanaging prepaid account funds transfers in some embodiments of thePAFT. In some implementations, the PAFT may enable a user to manage aprepaid account (e.g., manage transfer of funds to and from the prepaidaccount) via an interface. For example, the user may be able to managethe prepaid account via a web browser interface, e.g., 1101. In someimplementations, the user may be able to download an application (e.g.,an iPhone® app, Android™ app, HP Palm OS app, Windows® Mobile app,Blackberry® app, etc.) on to their client device, which may then providean interface for prepaid account management (see, e.g., 1112). Theinterface may provide notifications of the status of one or more prepaidaccount, e.g., 1102. For example, the interface may provide details suchas, but not limited to: number of accounts, account numbers, accountbalances, account transaction history, transaction history statistics(e.g., number of transactions within a predetermined/flexible timewindow, frequency of transactions, cumulative transaction amounts acrosstime, accounts, and/or other users, transactions by user, indications ofamount of bidirectionality of transfers, etc.), upcoming scheduledtransfer, and/or the like. In some implementations, the information suchas those listed above may be provided on a single screen simultaneously.In alternate implementations, the user interface may be designed as acomplex multiple-screen interface that may present detailed informationacross various types of analyses using multiple screens. In someimplementations, the interface may provide a listing of contacts, e.g.,1103. For example, the contacts listing may include a listing of othersusers with whom the user has engaged in prepaid account funds transfers(e.g., as transferor and/or transferee). In some implementations, theuser may be able to activate a link (see, e.g., 1104 a) to initiate atransfer with another user, and/or to create a transfer schedule forprepaid account funds transfers with that user. For example, one or moreuser(s) listed in the contacts listing may be selected simultaneously(e.g., by clicking a single user, selecting multiple users andactivating a graphical user interface element for initiating/schedulingtransfers with each of the selected users simultaneously), which whenactivated, provides the user an interface wherein the user can initiateand/or schedule prepaid account funds transfer(s) with the selecteduser(s) (see, e.g., 1104 b). In some implementations, the user interfacemay include one or more graphical user interface elements to provideinformation on upcoming scheduled transfers, e.g., graphical calendar1105 and textual schedule listing 1106. The graphical user elements mayprovide indication, alarms, notifications, etc. of due and/or upcomingtransfers. In some implementations, the PAFT may send alerts, notices,notifications, and/or the like to a contact of the user (e.g., pagernumber, mobile number, email address, postal address) for the user.

In some implementations, the user interface may provide various elementsfor inviting (see, e.g., 1107) other users to apply for obtaining newprepaid accounts with the PAFT. For example, the user interface mayprovide a hyperlink, e.g., 1108, upon activation of which the user maybe provided with graphical user interface elements to generate and sendinvitation requests for the PAFT. In various implementations, the usermay e able to invite other user to create prepaid accounts with the PAFTvia text message, e.g., 1109, phone, e.g., 1110, chat, socialnetworking, e.g., 1111, and/or the like.

PAFT Controller

FIG. 12 illustrates inventive aspects of a PAFT controller 1201 in ablock diagram. In this embodiment, the PAFT controller 1201 may serve toaggregate, process, store, search, serve, identify, instruct, generate,match, and/or facilitate interactions with a computer through varioustechnologies, and/or other related data.

Typically, users, which may be people and/or other systems, may engageinformation technology systems (e.g., computers) to facilitateinformation processing. In turn, computers employ processors to processinformation; such processors 1203 may be referred to as centralprocessing units (CPU). One form of processor is referred to as amicroprocessor. CPUs use communicative circuits to pass binary encodedsignals acting as instructions to enable various operations. Theseinstructions may be operational and/or data instructions containingand/or referencing other instructions and data in various processoraccessible and operable areas of memory 1229 (e.g., registers, cachememory, random access memory, etc.). Such communicative instructions maybe stored and/or transmitted in batches (e.g., batches of instructions)as programs and/or data components to facilitate desired operations.These stored instruction codes, e.g., programs, may engage the CPUcircuit components and other motherboard and/or system components toperform desired operations. One type of program is a computer operatingsystem, which, may be executed by CPU on a computer; the operatingsystem enables and facilitates users to access and operate computerinformation technology and resources. Some resources that may beemployed in information technology systems include: input and outputmechanisms through which data may pass into and out of a computer;memory storage into which data may be saved; and processors by whichinformation may be processed. These information technology systems maybe used to collect data for later retrieval, analysis, and manipulation,which may be facilitated through a database program. These informationtechnology systems provide interfaces that allow users to access andoperate various system components.

In one embodiment, the PAFT controller 1201 may be connected to and/orcommunicate with entities such as, but not limited to: one or more usersfrom user input devices 1211; peripheral devices 1212; an optionalcryptographic processor device 1228; and/or a communications network1213.

Networks are commonly thought to comprise the interconnection andinteroperation of clients, servers, and intermediary nodes in a graphtopology. It should be noted that the term “server” as used throughoutthis application refers generally to a computer, other device, program,or combination thereof that processes and responds to the requests ofremote users across a communications network. Servers serve theirinformation to requesting “clients.” The term “client” as used hereinrefers generally to a computer, program, other device, user and/orcombination thereof that is capable of processing and making requestsand obtaining and processing any responses from servers across acommunications network. A computer, other device, program, orcombination thereof that facilitates, processes information andrequests, and/or furthers the passage of information from a source userto a destination user is commonly referred to as a “node.” Networks aregenerally thought to facilitate the transfer of information from sourcepoints to destinations. A node specifically tasked with furthering thepassage of information from a source to a destination is commonly calleda “router.” There are many forms of networks such as Local Area Networks(LANs), Pico networks, Wide Area Networks (WANs), Wireless Networks(WLANs), etc. For example, the Internet is generally accepted as beingan interconnection of a multitude of networks whereby remote clients andservers may access and interoperate with one another.

The PAFT controller 1201 may be based on computer systems that maycomprise, but are not limited to, components such as: a computersystemization 1202 connected to memory 1229.

Computer Systemization

A computer systemization 1202 may comprise a clock 1230, centralprocessing unit (“CPU(s)” and/or “processor(s)” (these terms are usedinterchangeable throughout the disclosure unless noted to the contrary))1203, a memory 1229 (e.g., a read only memory (ROM) 1206, a randomaccess memory (RAM) 1205, etc.), and/or an interface bus 1207, and mostfrequently, although not necessarily, are all interconnected and/orcommunicating through a system bus 1204 on one or more (mother)board(s)1202 having conductive and/or otherwise transportive circuit pathwaysthrough which instructions (e.g., binary encoded signals) may travel toeffect communications, operations, storage, etc. Optionally, thecomputer systemization may be connected to an internal power source1286; e.g., optionally the power source may be internal. Optionally, acryptographic processor 1226 and/or transceivers (e.g., ICs) 1274 may beconnected to the system bus. In another embodiment, the cryptographicprocessor and/or transceivers may be connected as either internal and/orexternal peripheral devices 1212 via the interface bus I/O. In turn, thetransceivers may be connected to antenna(s) 1275, thereby effectuatingwireless transmission and reception of various communication and/orsensor protocols; for example the antenna(s) may connect to: a TexasInstruments WiLink WL1283 transceiver chip (e.g., providing 802.11n,Bluetooth 3.0, FM, global positioning system (GPS) (thereby allowingPAFT controller to determine its location)); Broadcom BCM4329FKUBGtransceiver chip (e.g., providing 802.11n, Bluetooth 2.1+ EDR, FM,etc.); a Broadcom BCM4750IUB8 receiver chip (e.g., GPS); an InfineonTechnologies X-Gold 618-PMB9800 (e.g., providing 2G/3G HSDPA/HSUPAcommunications); and/or the like. The system clock typically has acrystal oscillator and generates a base signal through the computersystemization's circuit pathways. The clock is typically coupled to thesystem bus and various clock multipliers that will increase or decreasethe base operating frequency for other components interconnected in thecomputer systemization. The clock and various components in a computersystemization drive signals embodying information throughout the system.Such transmission and reception of instructions embodying informationthroughout a computer systemization may be commonly referred to ascommunications. These communicative instructions may further betransmitted, received, and the cause of return and/or replycommunications beyond the instant computer systemization to:communications networks, input devices, other computer systemizations,peripheral devices, and/or the like. Of course, any of the abovecomponents may be connected directly to one another, connected to theCPU, and/or organized in numerous variations employed as exemplified byvarious computer systems.

The CPU comprises at least one high-speed data processor adequate toexecute program components for executing user and/or system-generatedrequests. Often, the processors themselves will incorporate variousspecialized processing units, such as, but not limited to: integratedsystem (bus) controllers, memory management control units, floatingpoint units, and even specialized processing sub-units like graphicsprocessing units, digital signal processing units, and/or the like.Additionally, processors may include internal fast access addressablememory, and be capable of mapping and addressing memory 529 beyond theprocessor itself; internal memory may include, but is not limited to:fast registers, various levels of cache memory (e.g., level 1, 2, 3,etc.), RAM, etc. The processor may access this memory through the use ofa memory address space that is accessible via instruction address, whichthe processor can construct and decode allowing it to access a circuitpath to a specific memory address space having a memory state. The CPUmay be a microprocessor such as: AMD's Athlon, Duron and/or Opteron;ARM's application, embedded and secure processors; IBM and/or Motorola'sDragonBall and PowerPC; IBM's and Sony's Cell processor; Intel'sCeleron, Core (2) Duo, Itanium, Pentium, Xeon, and/or XScale; and/or thelike processor(s). The CPU interacts with memory through instructionpassing through conductive and/or transportive conduits (e.g., (printed)electronic and/or optic circuits) to execute stored instructions (i.e.,program code) according to conventional data processing techniques. Suchinstruction passing facilitates communication within the PAFT controllerand beyond through various interfaces. Should processing requirementsdictate a greater amount speed and/or capacity, distributed processors(e.g., Distributed PAFT), mainframe, multi-core, parallel, and/orsuper-computer architectures may similarly be employed. Alternatively,should deployment requirements dictate greater portability, smallerPersonal Digital Assistants (PDAs) may be employed.

Depending on the particular implementation, features of the PAFT may beachieved by implementing a microcontroller such as CAST's R8051XC2microcontroller; Intel's MCS 51 (i.e., 8051 microcontroller); and/or thelike. Also, to implement certain features of the PAFT, some featureimplementations may rely on embedded components, such as:Application-Specific Integrated Circuit (“ASIC”), Digital SignalProcessing (“DSP”), Field Programmable Gate Array (“FPGA”), and/or thelike embedded technology. For example, any of the PAFT componentcollection (distributed or otherwise) and/or features may be implementedvia the microprocessor and/or via embedded components; e.g., via ASIC,coprocessor, DSP, FPGA, and/or the like. Alternately, someimplementations of the PAFT may be implemented with embedded componentsthat are configured and used to achieve a variety of features or signalprocessing.

Depending on the particular implementation, the embedded components mayinclude software solutions, hardware solutions, and/or some combinationof both hardware/software solutions. For example, PAFT featuresdiscussed herein may be achieved through implementing FPGAs, which are asemiconductor devices containing programmable logic components called“logic blocks”, and programmable interconnects, such as the highperformance FPGA Virtex series and/or the low cost Spartan seriesmanufactured by Xilinx. Logic blocks and interconnects can be programmedby the customer or designer, after the FPGA is manufactured, toimplement any of the PAFT features. A hierarchy of programmableinterconnects allow logic blocks to be interconnected as needed by thePAFT system designer/administrator, somewhat like a one-chipprogrammable breadboard. An FPGA's logic blocks can be programmed toperform the function of basic logic gates such as AND, and XOR, or morecomplex combinational functions such as decoders or simple mathematicalfunctions. In most FPGAs, the logic blocks also include memory elements,which may be simple flip-flops or more complete blocks of memory. Insome circumstances, the PAFT may be developed on regular FPGAs and thenmigrated into a fixed version that more resembles ASIC implementations.Alternate or coordinating implementations may migrate PAFT controllerfeatures to a final ASIC instead of or in addition to FPGAs. Dependingon the implementation all of the aforementioned embedded components andmicroprocessors may be considered the “CPU” and/or “processor” for thePAFT.

Power Source

The power source 1286 may be of any standard form for powering smallelectronic circuit board devices such as the following power cells:alkaline, lithium hydride, lithium ion, lithium polymer, nickel cadmium,solar cells, and/or the like. Other types of AC or DC power sources maybe used as well. In the case of solar cells, in one embodiment, the caseprovides an aperture through which the solar cell may capture photonicenergy. The power cell 1286 is connected to at least one of theinterconnected subsequent components of the PAFT thereby providing anelectric current to all subsequent components. In one example, the powersource 1286 is connected to the system bus component 1204. In analternative embodiment, an outside power source 1286 is provided througha connection across the I/O 1208 interface. For example, a USB and/orIEEE 1394 connection carries both data and power across the connectionand is therefore a suitable source of power.

Interface Adapters

Interface bus(ses) 1207 may accept, connect, and/or communicate to anumber of interface adapters, conventionally although not necessarily inthe form of adapter cards, such as but not limited to: input outputinterfaces (I/O) 1208, storage interfaces 1209, network interfaces 1210,and/or the like. Optionally, cryptographic processor interfaces 1227similarly may be connected to the interface bus. The interface busprovides for the communications of interface adapters with one anotheras well as with other components of the computer systemization.Interface adapters are adapted for a compatible interface bus. Interfaceadapters conventionally connect to the interface bus via a slotarchitecture. Conventional slot architectures may be employed, such as,but not limited to: Accelerated Graphics Port (AGP), Card Bus,(Extended) Industry Standard Architecture ((E)ISA), Micro ChannelArchitecture (MCA), NuBus, Peripheral Component Interconnect (Extended)(PCI(X)), PCI Express, Personal Computer Memory Card InternationalAssociation (PCMCIA), and/or the like.

Storage interfaces 1209 may accept, communicate, and/or connect to anumber of storage devices such as, but not limited to: storage devices1214, removable disc devices, and/or the like. Storage interfaces mayemploy connection protocols such as, but not limited to: (Ultra)(Serial) Advanced Technology Attachment (Packet Interface) ((Ultra)(Serial) ATA(PI)), (Enhanced) Integrated Drive Electronics ((E)IDE),Institute of Electrical and Electronics Engineers (IEEE) 1394, fiberchannel, Small Computer Systems Interface (SCSI), Universal Serial Bus(USB), and/or the like.

Network interfaces 1210 may accept, communicate, and/or connect to acommunications network 1213. Through a communications network 1213, thePAFT controller is accessible through remote clients 1233 b (e.g.,computers with web browsers) by users 1233 a. Network interfaces mayemploy connection protocols such as, but not limited to: direct connect,Ethernet (thick, thin, twisted pair 10/100/1000 Base T, and/or thelike), Token Ring, wireless connection such as IEEE 802.11a-x, and/orthe like. Should processing requirements dictate a greater amount speedand/or capacity, distributed network controllers (e.g., DistributedPAFT), architectures may similarly be employed to pool, load balance,and/or otherwise increase the communicative bandwidth required by thePAFT controller. A communications network may be any one and/or thecombination of the following: a direct interconnection; the Internet; aLocal Area Network (LAN); a Metropolitan Area Network (MAN); anOperating Missions as Nodes on the Internet (OMNI); a secured customconnection; a Wide Area Network (WAN); a wireless network (e.g.,employing protocols such as, but not limited to a Wireless ApplicationProtocol (WAP), I-mode, and/or the like); and/or the like. A networkinterface may be regarded as a specialized form of an input outputinterface. Further, multiple network interfaces 1210 may be used toengage with various communications network types 1213. For example,multiple network interfaces may be employed to allow for thecommunication over broadcast, multicast, and/or unicast networks.

Input Output interfaces (I/O) 1208 may accept, communicate, and/orconnect to user input devices 1211, peripheral devices 1212,cryptographic processor devices 1228, and/or the like. I/O may employconnection protocols such as, but not limited to: audio: analog,digital, monaural, RCA, stereo, and/or the like; data: Apple Desktop Bus(ADB), IEEE 1394a-b, serial, universal serial bus (USB); infrared;joystick; keyboard; midi; optical; PC AT; PS/2; parallel; radio; videointerface: Apple Desktop Connector (ADC), BNC, coaxial, component,composite, digital, Digital Visual Interface (DVI), high-definitionmultimedia interface (HDMI), RCA, RF antennae, S-Video, VGA, and/or thelike; wireless transceivers: 802.11a/b/g/n/x; Bluetooth; cellular (e.g.,code division multiple access (CDMA), high speed packet access(HSPA(+)), high-speed downlink packet access (HSDPA), global system formobile communications (GSM), long term evolution (LTE), WiMax, etc.);and/or the like. One typical output device may include a video display,which typically comprises a Cathode Ray Tube (CRT) or Liquid CrystalDisplay (LCD) based monitor with an interface (e.g., DVI circuitry andcable) that accepts signals from a video interface, may be used. Thevideo interface composites information generated by a computersystemization and generates video signals based on the compositedinformation in a video memory frame. Another output device is atelevision set, which accepts signals from a video interface. Typically,the video interface provides the composited video information through avideo connection interface that accepts a video display interface (e.g.,an RCA composite video connector accepting an RCA composite video cable;a DVI connector accepting a DVI display cable, etc.).

User input devices 1211 often are a type of peripheral device 512 (seebelow) and may include: card readers, dongles, finger print readers,gloves, graphics tablets, joysticks, keyboards, microphones, mouse(mice), remote controls, retina readers, touch screens (e.g.,capacitive, resistive, etc.), trackballs, trackpads, sensors (e.g.,accelerometers, ambient light, GPS, gyroscopes, proximity, etc.),styluses, and/or the like.

Peripheral devices 1212 may be connected and/or communicate to I/Oand/or other facilities of the like such as network interfaces, storageinterfaces, directly to the interface bus, system bus, the CPU, and/orthe like. Peripheral devices may be external, internal and/or part ofthe PAFT controller. Peripheral devices may include: antenna, audiodevices (e.g., line-in, line-out, microphone input, speakers, etc.),cameras (e.g., still, video, webcam, etc.), dongles (e.g., for copyprotection, ensuring secure transactions with a digital signature,and/or the like), external processors (for added capabilities; e.g.,crypto devices 528), force-feedback devices (e.g., vibrating motors),network interfaces, printers, scanners, storage devices, transceivers(e.g., cellular, GPS, etc.), video devices (e.g., goggles, monitors,etc.), video sources, visors, and/or the like. Peripheral devices ofteninclude types of input devices (e.g., cameras).

It should be noted that although user input devices and peripheraldevices may be employed, the PAFT controller may be embodied as anembedded, dedicated, and/or monitor-less (i.e., headless) device,wherein access would be provided over a network interface connection.

Cryptographic units such as, but not limited to, microcontrollers,processors 1226, interfaces 1227, and/or devices 1228 may be attached,and/or communicate with the PAFT controller. A MC68HC16 microcontroller,manufactured by Motorola Inc., may be used for and/or withincryptographic units. The MC68HC16 microcontroller utilizes a 16-bitmultiply-and-accumulate instruction in the 16 MHz configuration andrequires less than one second to perform a 512-bit RSA private keyoperation. Cryptographic units support the authentication ofcommunications from interacting agents, as well as allowing foranonymous transactions. Cryptographic units may also be configured aspart of CPU. Equivalent microcontrollers and/or processors may also beused. Other commercially available specialized cryptographic processorsinclude: the Broadcom's CryptoNetX and other Security Processors;nCipher's nShield, SafeNet's Luna PCI (e.g., 7100) series; SemaphoreCommunications' 40 MHz Roadrunner 184; Sun's Cryptographic Accelerators(e.g., Accelerator 6000 PCIe Board, Accelerator 500 Daughtercard); ViaNano Processor (e.g., L2100, L2200, U2400) line, which is capable ofperforming 500+ MB/s of cryptographic instructions; VLSI Technology's 33MHz 6868; and/or the like.

Memory

Generally, any mechanization and/or embodiment allowing a processor toaffect the storage and/or retrieval of information is regarded as memory1229. However, memory is a fungible technology and resource, thus, anynumber of memory embodiments may be employed in lieu of or in concertwith one another. It is to be understood that the PAFT controller and/ora computer systemization may employ various forms of memory 1229. Forexample, a computer systemization may be configured wherein thefunctionality of on-chip CPU memory (e.g., registers), RAM, ROM, and anyother storage devices are provided by a paper punch tape or paper punchcard mechanism; of course such an embodiment would result in anextremely slow rate of operation. In a typical configuration, memory1229 will include ROM 1206, RAM 1205, and a storage device 1214. Astorage device 1214 may be any conventional computer system storage.Storage devices may include a drum; a (fixed and/or removable) magneticdisk drive; a magneto-optical drive; an optical drive (i.e., Blueray, CDROM/RAM/Recordable (R)/ReWritable (RW), DVD R/RW, HD DVD R/RW etc.); anarray of devices (e.g., Redundant Array of Independent Disks (RAID));solid state memory devices (USB memory, solid state drives (SSD), etc.);other processor-readable storage mediums; and/or other devices of thelike. Thus, a computer systemization generally requires and makes use ofmemory.

Component Collection

The memory 1229 may contain a collection of program and/or databasecomponents and/or data such as, but not limited to: operating systemcomponent(s) 1215 (operating system); information server component(s)1216 (information server); user interface component(s) 1217 (userinterface); Web browser component(s) 1218 (Web browser); database(s)1219; mail server component(s) 1221; mail client component(s) 1222;cryptographic server component(s) 1220 (cryptographic server); the PAFTcomponent(s) 1235; and/or the like (i.e., collectively a componentcollection). These components may be stored and accessed from thestorage devices and/or from storage devices accessible through aninterface bus. Although non-conventional program components such asthose in the component collection, typically, are stored in a localstorage device 1214, they may also be loaded and/or stored in memorysuch as: peripheral devices, RAM, remote storage facilities through acommunications network, ROM, various forms of memory, and/or the like.

Operating System

The operating system component 1215 is an executable program componentfacilitating the operation of the PAFT controller. Typically, theoperating system facilitates access of I/O, network interfaces,peripheral devices, storage devices, and/or the like. The operatingsystem may be a highly fault tolerant, scalable, and secure system suchas: Apple Macintosh OS X (Server); AT&T Nan 9; Be OS; Unix and Unix-likesystem distributions (such as AT&T's UNIX; Berkley Software Distribution(BSD) variations such as FreeBSD, NetBSD, OpenBSD, and/or the like;Linux distributions such as Red Hat, Ubuntu, and/or the like); and/orthe like operating systems. However, more limited and/or less secureoperating systems also may be employed such as Apple Macintosh OS, IBMOS/2, Microsoft DOS, Microsoft Windows2000/2003/3.1/95/98/CE/Millenium/NT/Vista/XP (Server), Palm OS, and/orthe like. An operating system may communicate to and/or with othercomponents in a component collection, including itself, and/or the like.Most frequently, the operating system communicates with other programcomponents, user interfaces, and/or the like. For example, the operatingsystem may contain, communicate, generate, obtain, and/or provideprogram component, system, user, and/or data communications, requests,and/or responses. The operating system, once executed by the CPU, mayenable the interaction with communications networks, data, I/O,peripheral devices, program components, memory, user input devices,and/or the like. The operating system may provide communicationsprotocols that allow the PAFT controller to communicate with otherentities through a communications network 1213. Various communicationprotocols may be used by the PAFT controller as a subcarrier transportmechanism for interaction, such as, but not limited to: multicast,TCP/IP, UDP, unicast, and/or the like.

Information Server

An information server component 1216 is a stored program component thatis executed by a CPU. The information server may be a conventionalInternet information server such as, but not limited to Apache SoftwareFoundation's Apache, Microsoft's Internet Information Server, and/or thelike. The information server may allow for the execution of programcomponents through facilities such as Active Server Page (ASP), ActiveX,(ANSI) (Objective−) C (++), C# and/or .NET, Common Gateway Interface(CGI) scripts, dynamic (D) hypertext markup language (HTML), FLASH,Java, JavaScript, Practical Extraction Report Language (PERL), HypertextPre-Processor (PHP), pipes, Python, wireless application protocol (WAP),WebObjects, and/or the like. The information server may support securecommunications protocols such as, but not limited to, File TransferProtocol (FTP); HyperText Transfer Protocol (HTTP); Secure HypertextTransfer Protocol (HTTPS), Secure Socket Layer (SSL), messagingprotocols (e.g., America Online (AOL) Instant Messenger (AIM),Application Exchange (APEX), ICQ, Internet Relay Chat (IRC), MicrosoftNetwork (MSN) Messenger Service, Presence and Instant Messaging Protocol(PRIM), Internet Engineering Task Force's (IETF's) Session InitiationProtocol (SIP), SIP for Instant Messaging and Presence LeveragingExtensions (SIMPLE), open XML-based Extensible Messaging and PresenceProtocol (XMPP) (i.e., Jabber or Open Mobile Alliance's (OMA's) InstantMessaging and Presence Service (IMPS)), Yahoo! Instant MessengerService, and/or the like. The information server provides results in theform of Web pages to Web browsers, and allows for the manipulatedgeneration of the Web pages through interaction with other programcomponents. After a Domain Name System (DNS) resolution portion of anHTTP request is resolved to a particular information server, theinformation server resolves requests for information at specifiedlocations on the PAFT controller based on the remainder of the HTTPrequest. For example, a request such ashttp://123.124.125.126/myInformation.html might have the IP portion ofthe request “123.124.125.126” resolved by a DNS server to an informationserver at that IP address; that information server might in turn furtherparse the http request for the “/myInformation.html” portion of therequest and resolve it to a location in memory containing theinformation “myInformation.html.” Additionally, other informationserving protocols may be employed across various ports, e.g., FTPcommunications across port 21, and/or the like. An information servermay communicate to and/or with other components in a componentcollection, including itself, and/or facilities of the like. Mostfrequently, the information server communicates with the PAFT database1219, operating systems, other program components, user interfaces, Webbrowsers, and/or the like.

Access to the PAFT database may be achieved through a number of databasebridge mechanisms such as through scripting languages as enumeratedbelow (e.g., CGI) and through inter-application communication channelsas enumerated below (e.g., CORBA, WebObjects, etc.). Any data requeststhrough a Web browser are parsed through the bridge mechanism intoappropriate grammars as required by the PAFT. In one embodiment, theinformation server would provide a Web form accessible by a Web browser.Entries made into supplied fields in the Web form are tagged as havingbeen entered into the particular fields, and parsed as such. The enteredterms are then passed along with the field tags, which act to instructthe parser to generate queries directed to appropriate tables and/orfields. In one embodiment, the parser may generate queries in standardSQL by instantiating a search string with the proper join/selectcommands based on the tagged text entries, wherein the resulting commandis provided over the bridge mechanism to the PAFT as a query. Upongenerating query results from the query, the results are passed over thebridge mechanism, and may be parsed for formatting and generation of anew results Web page by the bridge mechanism. Such a new results Webpage is then provided to the information server, which may supply it tothe requesting Web browser.

Also, an information server may contain, communicate, generate, obtain,and/or provide program component, system, user, and/or datacommunications, requests, and/or responses.

User Interface

Computer interfaces in some respects are similar to automobile operationinterfaces. Automobile operation interface elements such as steeringwheels, gearshifts, and speedometers facilitate the access, operation,and display of automobile resources, and status. Computer interactioninterface elements such as check boxes, cursors, menus, scrollers, andwindows (collectively and commonly referred to as widgets) similarlyfacilitate the access, capabilities, operation, and display of data andcomputer hardware and operating system resources, and status. Operationinterfaces are commonly called user interfaces. Graphical userinterfaces (GUIs) such as the Apple Macintosh Operating System's Aqua,IBM's OS/2, Microsoft's Windows2000/2003/3.1/95/98/CE/Millenium/NT/XP/Vista/7 (i.e., Aero), Unix'sX-Windows (e.g., which may include additional Unix graphic interfacelibraries and layers such as K Desktop Environment (KDE), mythTV and GNUNetwork Object Model Environment (GNOME)), web interface libraries(e.g., ActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, etc. interfacelibraries such as, but not limited to, Dojo, jQuery(UI), MooTools,Prototype, script.aculo.us, SWFObject, Yahoo! User Interface, any ofwhich may be used and) provide a baseline and means of accessing anddisplaying information graphically to users.

A user interface component 1217 is a stored program component that isexecuted by a CPU. The user interface may be a conventional graphic userinterface as provided by, with, and/or atop operating systems and/oroperating environments such as already discussed. The user interface mayallow for the display, execution, interaction, manipulation, and/oroperation of program components and/or system facilities through textualand/or graphical facilities. The user interface provides a facilitythrough which users may affect, interact, and/or operate a computersystem. A user interface may communicate to and/or with other componentsin a component collection, including itself, and/or facilities of thelike. Most frequently, the user interface communicates with operatingsystems, other program components, and/or the like. The user interfacemay contain, communicate, generate, obtain, and/or provide programcomponent, system, user, and/or data communications, requests, and/orresponses.

Web Browser

A Web browser component 1218 is a stored program component that isexecuted by a CPU. The Web browser may be a conventional hypertextviewing application such as Microsoft Internet Explorer or NetscapeNavigator. Secure Web browsing may be supplied with 128 bit (or greater)encryption by way of HTTPS, SSL, and/or the like. Web browsers allowingfor the execution of program components through facilities such asActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, web browser plug-inAPIs (e.g., FireFox, Safari Plug-in, and/or the like APIs), and/or thelike. Web browsers and like information access tools may be integratedinto PDAs, cellular telephones, and/or other mobile devices. A Webbrowser may communicate to and/or with other components in a componentcollection, including itself, and/or facilities of the like. Mostfrequently, the Web browser communicates with information servers,operating systems, integrated program components (e.g., plug-ins),and/or the like; e.g., it may contain, communicate, generate, obtain,and/or provide program component, system, user, and/or datacommunications, requests, and/or responses. Of course, in place of a Webbrowser and information server, a combined application may be developedto perform similar functions of both. The combined application wouldsimilarly affect the obtaining and the provision of information tousers, user agents, and/or the like from the PAFT enabled nodes. Thecombined application may be nugatory on systems employing standard Webbrowsers.

Mail Server

A mail server component 1221 is a stored program component that isexecuted by a CPU 1203. The mail server may be a conventional Internetmail server such as, but not limited to sendmail, Microsoft Exchange,and/or the like. The mail server may allow for the execution of programcomponents through facilities such as ASP, ActiveX, (ANSI) (Objective−)C (++), C# and/or .NET, CGI scripts, Java, JavaScript, PERL, PHP, pipes,Python, WebObjects, and/or the like. The mail server may supportcommunications protocols such as, but not limited to: Internet messageaccess protocol (IMAP), Messaging Application Programming Interface(MAPI)/Microsoft Exchange, post office protocol (POPS), simple mailtransfer protocol (SMTP), and/or the like. The mail server can route,forward, and process incoming and outgoing mail messages that have beensent, relayed and/or otherwise traversing through and/or to the PAFT.

Access to the PAFT mail may be achieved through a number of APIs offeredby the individual Web server components and/or the operating system.

Also, a mail server may contain, communicate, generate, obtain, and/orprovide program component, system, user, and/or data communications,requests, information, and/or responses.

Mail Client

A mail client component 1222 is a stored program component that isexecuted by a CPU 1203. The mail client may be a conventional mailviewing application such as Apple Mail, Microsoft Entourage, MicrosoftOutlook, Microsoft Outlook Express, Mozilla, Thunderbird, and/or thelike. Mail clients may support a number of transfer protocols, such as:IMAP, Microsoft Exchange, POPS, SMTP, and/or the like. A mail client maycommunicate to and/or with other components in a component collection,including itself, and/or facilities of the like. Most frequently, themail client communicates with mail servers, operating systems, othermail clients, and/or the like; e.g., it may contain, communicate,generate, obtain, and/or provide program component, system, user, and/ordata communications, requests, information, and/or responses. Generally,the mail client provides a facility to compose and transmit electronicmail messages.

Cryptographic Server

A cryptographic server component 1220 is a stored program component thatis executed by a CPU 1203, cryptographic processor 1226, cryptographicprocessor interface 1227, cryptographic processor device 1228, and/orthe like. Cryptographic processor interfaces will allow for expeditionof encryption and/or decryption requests by the cryptographic component;however, the cryptographic component, alternatively, may run on aconventional CPU. The cryptographic component allows for the encryptionand/or decryption of provided data. The cryptographic component allowsfor both symmetric and asymmetric (e.g., Pretty Good Protection (PGP))encryption and/or decryption. The cryptographic component may employcryptographic techniques such as, but not limited to: digitalcertificates (e.g., X.509 authentication framework), digital signatures,dual signatures, enveloping, password access protection, public keymanagement, and/or the like. The cryptographic component will facilitatenumerous (encryption and/or decryption) security protocols such as, butnot limited to: checksum, Data Encryption Standard (DES), EllipticalCurve Encryption (ECC), International Data Encryption Algorithm (IDEA),Message Digest 5 (MD5, which is a one way hash function), passwords,Rivest Cipher (RC5), Rijndael, RSA (which is an Internet encryption andauthentication system that uses an algorithm developed in 1977 by RonRivest, Adi Shamir, and Leonard Adleman), Secure Hash Algorithm (SHA),Secure Socket Layer (SSL), Secure Hypertext Transfer Protocol (HTTPS),and/or the like. Employing such encryption security protocols, the PAFTmay encrypt all incoming and/or outgoing communications and may serve asnode within a virtual private network (VPN) with a wider communicationsnetwork. The cryptographic component facilitates the process of“security authorization” whereby access to a resource is inhibited by asecurity protocol wherein the cryptographic component effects authorizedaccess to the secured resource. In addition, the cryptographic componentmay provide unique identifiers of content, e.g., employing and MD5 hashto obtain a unique signature for an digital audio file. A cryptographiccomponent may communicate to and/or with other components in a componentcollection, including itself, and/or facilities of the like. Thecryptographic component supports encryption schemes allowing for thesecure transmission of information across a communications network toenable the PAFT component to engage in secure transactions if sodesired. The cryptographic component facilitates the secure accessing ofresources on the PAFT and facilitates the access of secured resources onremote systems; i.e., it may act as a client and/or server of securedresources. Most frequently, the cryptographic component communicateswith information servers, operating systems, other program components,and/or the like. The cryptographic component may contain, communicate,generate, obtain, and/or provide program component, system, user, and/ordata communications, requests, and/or responses.

The PAFT Database

The PAFT database component 1219 may be embodied in a database and itsstored data. The database is a stored program component, which isexecuted by the CPU; the stored program component portion configuringthe CPU to process the stored data. The database may be a conventional,fault tolerant, relational, scalable, secure database such as Oracle orSybase. Relational databases are an extension of a flat file. Relationaldatabases consist of a series of related tables. The tables areinterconnected via a key field. Use of the key field allows thecombination of the tables by indexing against the key field; i.e., thekey fields act as dimensional pivot points for combining informationfrom various tables. Relationships generally identify links maintainedbetween tables by matching primary keys. Primary keys represent fieldsthat uniquely identify the rows of a table in a relational database.More precisely, they uniquely identify rows of a table on the “one” sideof a one-to-many relationship.

Alternatively, the PAFT database may be implemented using variousstandard data-structures, such as an array, hash, (linked) list, struct,structured text file (e.g., XML), table, and/or the like. Suchdata-structures may be stored in memory and/or in (structured) files. Inanother alternative, an object-oriented database may be used, such asFrontier, ObjectStore, Poet, Zope, and/or the like. Object databases caninclude a number of object collections that are grouped and/or linkedtogether by common attributes; they may be related to other objectcollections by some common attributes. Object-oriented databases performsimilarly to relational databases with the exception that objects arenot just pieces of data but may have other types of functionalityencapsulated within a given object. If the PAFT database is implementedas a data-structure, the use of the PAFT database 1219 may be integratedinto another component such as the PAFT component 1235. Also, thedatabase may be implemented as a mix of data structures, objects, andrelational structures. Databases may be consolidated and/or distributedin countless variations through standard data processing techniques.Portions of databases, e.g., tables, may be exported and/or imported andthus decentralized and/or integrated.

In one embodiment, the database component 1219 includes several tables1219 a-k. A User table 1219 a may include fields such as, but notlimited to: user_id, applicant_id, firstname, lastname, address_line1,address_line2, dob, ssn, credit_check_flag, zipcode, city, state,account_params_list, account_mode, account_type, account_expiry,preferred_bank_name, preferred_branch_name, credit_report, and/or thelike. The User table may support and/or track multiple entity accountson a PAFT. A Clients table 1219 b may include fields such as, but notlimited to: client_ID, client_type, client_MAC, client_IP,presentation_format, pixel_count, resolution, screen_size,audio_fidelity, hardware_settings_list, software_compatibilities_list,installed_apps_list, and/or the like. An Invitations table 1219 c mayinclude fields such as, but not limited to: request_id, timestamp,transferor_id, client_IP, transferee_details_list, transferee_type,first_name, last_name, contact_type, contact_info, alt_contact_info,alt_contact_type, alt_contact_info, client_type, num_invite_attempts,account_params_list, same_bank_flag, same_branch_flag,persistent_link_flag, transfer_param_list, on_schedule_flag,one_time_flag, amount, instant_transfer_flag, custom_invitation,transferee_details_list, transferee_client_IP, and/or the like. A Formstable 1219 d may include fields such as, but not limited to:invitation_template_list, invitation_type, invitation_data, and/or thelike. A Clearance table 1219 e may include fields such as, but notlimited to: applicant_firstname, applicant_lastname,applicant_address_line1, applicant_address_line2,consumer_bureau_data_list, consumer_bureau_data, applicant_clear_flag,credit_limit, credit_score, account_balances, delinquency_flag,quality_flags, and/or the like. A Links table 1219 f may include fieldssuch as, but not limited to: timestamp, link_ID, bidirectional_flag,transferor_ID, transferor_account_num, transferor_bank,transferor_branch, transferor_ABA, transferee_ID,transferee_account_num, transferee_bank, transferee_branch,transferee_ABA, and/or the like. A Schedules table 1219 g may includefields such as, but not limited to: timestamp, transferor_ID,transferee_ID, link_ID, num_transfers transfer_date, transfer_frequency,transfer_interval, notify_transfers_settings, and/or the like. A BankAccounts table 1219 h may include fields such as, but not limited to:account_id, account_firstname, account_lastname, accountholder_type,account_type, contact_type, contact_info, opening_balance,current_balance, and/or the like. A Transfers table 1219 i may includefields such as, but not limited to: transfer_ID, transferor_ID,transferee_ID, link_ID, transfer_amount, timestamp,notify_transfers_flags, and/or the like. An App Modules table 1219 j mayinclude fields such as, but not limited to: app_ID, app_name, app_type,OS_compatibilities_list, version, timestamp, developer_ID, and/or thelike. A Market Data table 1219 k may include fields such as, but notlimited to: market_data_feed_ID, asset_ID, asset_symbol, asset_name,spot_price, bid_price, ask_price, and/or the like; in one embodiment,the market data table is populated through a market data feed (e.g.,Bloomberg's PhatPipe, Dun & Bradstreet, Reuter's Tib, Triarch, etc.),for example, through Microsoft's Active Template Library and DealingObject Technology's real-time toolkit Rtt.Multi.

In one embodiment, the PAFT database may interact with other databasesystems. For example, employing a distributed database system, queriesand data access by search PAFT component may treat the combination ofthe PAFT database, an integrated data security layer database as asingle database entity.

In one embodiment, user programs may contain various user interfaceprimitives, which may serve to update the PAFT. Also, various accountsmay require custom database tables depending upon the environments andthe types of clients the PAFT may need to serve. It should be noted thatany unique fields may be designated as a key field throughout. In analternative embodiment, these tables have been decentralized into theirown databases and their respective database controllers (i.e.,individual database controllers for each of the above tables). Employingstandard data processing techniques, one may further distribute thedatabases over several computer systemizations and/or storage devices.Similarly, configurations of the decentralized database controllers maybe varied by consolidating and/or distributing the various databasecomponents 1219 a-k. The PAFT may be configured to keep track of varioussettings, inputs, and parameters via database controllers.

The PAFT database may communicate to and/or with other components in acomponent collection, including itself, and/or facilities of the like.Most frequently, the PAFT database communicates with the PAFT component,other program components, and/or the like. The database may contain,retain, and provide information regarding other nodes and data.

The PAFTs

The PAFT component 1235 is a stored program component that is executedby a CPU. In one embodiment, the PAFT component incorporates any and/orall combinations of the aspects of the PAFT discussed in the previousfigures. As such, the PAFT affects accessing, obtaining and theprovision of information, services, transactions, and/or the like acrossvarious communications networks.

The PAFT component may transform prepaid account invitation requests viaPAFT components into scheduled prepaid account transactions, and/or thelike and use of the PAFT. In one embodiment, the PAFT component 1235takes inputs (e.g., invitation request input 211, invitation template216, invitation acceptance input 411, invitation type 416, prepaidaccount application form 419, application form input 423, applicantscreening failure report 428 a, applicant screening success report 428b, payment order input 611 a, receivables request input 611 b, transferschedule 612 c, transfer link data 615, user profile data 617, and/orthe like) etc., and transforms the inputs via various components (e.g.,PAM component 1241, PAR component 1242, Tr-FTT component 1243, Te-FTTcomponent 1244, S-FTT component 1245, PA-FTP component 1246, and/or thelike), into outputs (e.g., invitation data 218, customized prepaidaccount invitation 219, invitation confirmation message 222, prepaidaccount application form 420, application denial notification 429 a,prepaid account opening request message 430 b, account issue message436, user profile 438, prepaid account link data 439, prepaid accountfunds transfer schedule 440, transaction data 622, transactionsnotifications 623 a-b, and/or the like).

The PAFT component enabling access of information between nodes may bedeveloped by employing standard development tools and languages such as,but not limited to: Apache components, Assembly, ActiveX, binaryexecutables, (ANSI) (Objective−) C (++), C# and/or .NET, databaseadapters, CGI scripts, Java, JavaScript, mapping tools, procedural andobject oriented development tools, PERL, PHP, Python, shell scripts, SQLcommands, web application server extensions, web developmentenvironments and libraries (e.g., Microsoft's ActiveX; Adobe AIR, FLEX &FLASH; AJAX; (D)HTML; Dojo, Java; JavaScript; jQuery(UI); MooTools;Prototype; script.aculo.us; Simple Object Access Protocol (SOAP);SWFObject; Yahoo! User Interface; and/or the like), WebObjects, and/orthe like. In one embodiment, the PAFT server employs a cryptographicserver to encrypt and decrypt communications. The PAFT component maycommunicate to and/or with other components in a component collection,including itself, and/or facilities of the like. Most frequently, thePAFT component communicates with the PAFT database, operating systems,other program components, and/or the like. The PAFT may contain,communicate, generate, obtain, and/or provide program component, system,user, and/or data communications, requests, and/or responses.

Distributed PAFTs

The structure and/or operation of any of the PAFT node controllercomponents may be combined, consolidated, and/or distributed in anynumber of ways to facilitate development and/or deployment. Similarly,the component collection may be combined in any number of ways tofacilitate deployment and/or development. To accomplish this, one mayintegrate the components into a common code base or in a facility thatcan dynamically load the components on demand in an integrated fashion.

The component collection may be consolidated and/or distributed incountless variations through standard data processing and/or developmenttechniques. Multiple instances of any one of the program components inthe program component collection may be instantiated on a single node,and/or across numerous nodes to improve performance throughload-balancing and/or data-processing techniques. Furthermore, singleinstances may also be distributed across multiple controllers and/orstorage devices; e.g., databases. All program component instances andcontrollers working in concert may do so through standard dataprocessing communication techniques.

The configuration of the PAFT controller will depend on the context ofsystem deployment. Factors such as, but not limited to, the budget,capacity, location, and/or use of the underlying hardware resources mayaffect deployment requirements and configuration. Regardless of if theconfiguration results in more consolidated and/or integrated programcomponents, results in a more distributed series of program components,and/or results in some combination between a consolidated anddistributed configuration, data may be communicated, obtained, and/orprovided. Instances of components consolidated into a common code basefrom the program component collection may communicate, obtain, and/orprovide data. This may be accomplished through intra-application dataprocessing communication techniques such as, but not limited to: datareferencing (e.g., pointers), internal messaging, object instancevariable communication, shared memory space, variable passing, and/orthe like.

If component collection components are discrete, separate, and/orexternal to one another, then communicating, obtaining, and/or providingdata with and/or to other component components may be accomplishedthrough inter-application data processing communication techniques suchas, but not limited to: Application Program Interfaces (API) informationpassage; (distributed) Component Object Model ((D)COM), (Distributed)Object Linking and Embedding ((D)OLE), and/or the like), Common ObjectRequest Broker Architecture (CORBA), Jini local and remote applicationprogram interfaces, JavaScript Object Notation (JSON), Remote MethodInvocation (RMI), SOAP, process pipes, shared files, and/or the like.Messages sent between discrete component components forinter-application communication or within memory spaces of a singularcomponent for intra-application communication may be facilitated throughthe creation and parsing of a grammar. A grammar may be developed byusing development tools such as lex, yacc, XML, and/or the like, whichallow for grammar generation and parsing capabilities, which in turn mayform the basis of communication messages within and between components.

For example, a grammar may be arranged to recognize the tokens of anHTTP post command, e.g.:

-   -   w3c -post http:// . . . Value1

where Value1 is discerned as being a parameter because “http://” is partof the grammar syntax, and what follows is considered part of the postvalue. Similarly, with such a grammar, a variable “Value1” may beinserted into an “http://” post command and then sent. The grammarsyntax itself may be presented as structured data that is interpretedand/or otherwise used to generate the parsing mechanism (e.g., a syntaxdescription text file as processed by lex, yacc, etc.). Also, once theparsing mechanism is generated and/or instantiated, it itself mayprocess and/or parse structured data such as, but not limited to:character (e.g., tab) delineated text, HTML, structured text streams,XML, and/or the like structured data. In another embodiment,inter-application data processing protocols themselves may haveintegrated and/or readily available parsers (e.g., JSON, SOAP, and/orlike parsers) that may be employed to parse (e.g., communications) data.Further, the parsing grammar may be used beyond message parsing, but mayalso be used to parse: databases, data collections, data stores,structured data, and/or the like. Again, the desired configuration willdepend upon the context, environment, and requirements of systemdeployment.

For example, in some implementations, the PAFT controller may beexecuting a PHP script implementing a Secure Sockets Layer (“SSL”)socket server via the information server, which listens to incomingcommunications on a server port to which a client may send data, e.g.,data encoded in JSON format. Upon identifying an incoming communication,the PHP script may read the incoming message from the client device,parse the received JSON-encoded text data to extract information fromthe JSON-encoded text data into PHP script variables, and store the data(e.g., client identifying information, etc.) and/or extractedinformation in a relational database accessible using the StructuredQuery Language (“SQL”). An example listing, written substantially in theform of PHP/SQL commands, to accept JSON-encoded input data from aclient device via a SSL connection, parse the data to extract variables,and store the data to a database, is provided below:

<?PHP header(‘Content-Type: text/plain’); // set ip address and port tolisten to for incoming data $address = ‘192.168.0.100’; $port = 255; //create a server-side SSL socket, listen for/accept incomingcommunication $sock = socket_create(AF_INET, SOCK_STREAM, 0);socket_bind($sock, $address, $port) or die(‘Could not bind to address’);socket_listen($sock); $client = socket_accept($sock); // read input datafrom client device in 1024 byte blocks until end of message do {    $input = “”;     $input = socket_read($client, 1024);     $data .=$input; } while($input != “”); // parse data to extract variables $obj =json_decode($data, true); // store input data in a databasemysql_connect(“201.408.185.132”,$DBserver,$password); // access databaseserver mysql_select(“CLIENT_DB.SQL”); // select database to appendmysql_query(“INSERT INTO UserTable (transmission) VALUES ($data)”); //add data to UserTable table in a CLIENT databasemysql_close(“CLIENT_DB.SQL”); // close connection to database ?>

Also, the following resources may be used to provide example embodimentsregarding SOAP parser implementation:

http://www.xav.com/perl/site/lib/SOAP/Parser.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/Index.jsp?topic=/com.ibm.IBMDI.doc/referenceguide295.htmand other parser implementations:

http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.IBMDI.doc/referenceguide259.htmall of which are hereby expressly incorporated by reference.

In order to address various issues and advance the art, the entirety ofthis application for PREPAID ACCOUNT FUNDS TRANSFER APPARATUSES, METHODSAND SYSTEMS (including the Cover Page, Title, Headings, Field,Background, Summary, Brief Description of the Drawings, DetailedDescription, Claims, Abstract, Figures, Appendices and/or otherwise)shows by way of illustration various embodiments in which the claimedinventions may be practiced. The advantages and features of theapplication are of a representative sample of embodiments only, and arenot exhaustive and/or exclusive. They are presented only to assist inunderstanding and teach the claimed principles. It should be understoodthat they are not representative of all claimed inventions. As such,certain aspects of the disclosure have not been discussed herein. Thatalternate embodiments may not have been presented for a specific portionof the invention or that further undescribed alternate embodiments maybe available for a portion is not to be considered a disclaimer of thosealternate embodiments. It will be appreciated that many of thoseundescribed embodiments incorporate the same principles of the inventionand others are equivalent. Thus, it is to be understood that otherembodiments may be utilized and functional, logical, organizational,structural and/or topological modifications may be made withoutdeparting from the scope and/or spirit of the disclosure. As such, allexamples and/or embodiments are deemed to be non-limiting throughoutthis disclosure. Also, no inference should be drawn regarding thoseembodiments discussed herein relative to those not discussed hereinother than it is as such for purposes of reducing space and repetition.For instance, it is to be understood that the logical and/or topologicalstructure of any combination of any program components (a componentcollection), other components and/or any present feature sets asdescribed in the figures and/or throughout are not limited to a fixedoperating order and/or arrangement, but rather, any disclosed order isexemplary and all equivalents, regardless of order, are contemplated bythe disclosure. Furthermore, it is to be understood that such featuresare not limited to serial execution, but rather, any number of threads,processes, services, servers, and/or the like that may executeasynchronously, concurrently, in parallel, simultaneously,synchronously, and/or the like are contemplated by the disclosure. Assuch, some of these features may be mutually contradictory, in that theycannot be simultaneously present in a single embodiment. Similarly, somefeatures are applicable to one aspect of the invention, and inapplicableto others. In addition, the disclosure includes other inventions notpresently claimed. Applicant reserves all rights in those presentlyunclaimed inventions including the right to claim such inventions, fileadditional applications, continuations, continuations in part,divisions, and/or the like thereof. As such, it should be understoodthat advantages, embodiments, examples, functional, features, logical,organizational, structural, topological, and/or other aspects of thedisclosure are not to be considered limitations on the disclosure asdefined by the claims or limitations on equivalents to the claims. It isto be understood that, depending on the particular needs and/orcharacteristics of a PAFT individual and/or enterprise user, databaseconfiguration and/or relational model, data type, data transmissionand/or network framework, syntax structure, and/or the like, variousembodiments of the PAFT may be implemented that enable a great deal offlexibility and customization. For example, aspects of the PAFT may beadapted for credit cards, certificates of deposit (CDs), money marketaccounts, stock purchases, trading systems, mortgages, insurancepolicies, and/or the like. In general, it is contemplated that aspectsof the PAFT may be adapted for any mode of transfer of wealth from oneentity to another. While various embodiments and discussions of the PAFThave been directed to account-based transactions, however, it is to beunderstood that the embodiments described herein may be readilyconfigured and/or customized for a wide variety of other applicationsand/or implementations.

What is claimed is:
 1. A prepaid account funds transferprocessor-implemented method for automatically scheduling a prepaidfunds transfer based on a prepaid accounts receivable request,comprising: receiving at a prepaid accounts receivable request server,via an electronic payment processing network, from a transferee userholding a transferee prepaid account, a prepaid account receivablesrequest specifying i) a transferee user identifier and ii) a prepaidfunds transfer amount to be transferred from a transferor prepaidaccount of the transferor user to the transferee prepaid account of thetransferee user; in response to receiving the prepaid accountreceivables request, retrieving, via the prepaid accounts receivablerequest server, a prepaid account link data record based on the receivedtransferee user identifier from a links database, the prepaid link datarecord i) providing a link between the transferor prepaid account andthe transferee prepaid account and ii) being generated at the time ofcreation of the transferee prepaid account; determining, via the prepaidaccounts receivable request server, using the retrieved prepaid accountlink data record, the transferor prepaid account that is linked with thetransferee prepaid account; and generating, via the prepaid accountsreceivable request server, a prepaid account funds transfer schedulerecord for storage in a schedules database, the prepaid account fundstransfer schedule record indicating a date when the prepaid fundstransfer amount of funds specified in the prepaid account receivablesrequest are to be automatically transferred from the transferor prepaidaccount to the transferee prepaid account.
 2. The method of claim 1,wherein creation of the transferee prepaid account is contingent uponthe transferee user passing a screening test based on the completedprepaid account application.
 3. The method of claim 1, wherein thetransferee prepaid account is created locally.
 4. The method of claim 1,further comprising: transferring a scheduled transfer amount from thetransferor prepaid account to the created transferee prepaid accountbased on the generated prepaid account funds transfer schedule.
 5. Themethod of claim 4, wherein at least one scheduled funds transferincluded in the prepaid account funds transfer schedule specifiestransferring funds from the transferee prepaid account to the transferorprepaid account.
 6. A prepaid account funds transfer system forautomatically scheduling a prepaid funds transfer based on a prepaidaccounts receivable request, comprising: a prepaid accounts receivablerequest server that includes a memory and a processor communicativelycoupled with the memory, the prepaid accounts receivable request serverconfigured to: receive at the prepaid accounts receivable requestserver, via an electronic payment processing network, from a transfereeuser holding a transferee prepaid account, a prepaid account receivablesrequest specifying i) a transferee user identifier and ii) a prepaidfunds transfer amount to be transferred from a transferor prepaidaccount of the transferor user to the transferee prepaid account of thetransferee user; in response to receiving the prepaid accountreceivables request, retrieve, via the prepaid accounts receivablerequest server, a prepaid account link data record based on the receivedtransferee user identifier from a links database, the prepaid link datarecord i) providing a link between the transferor prepaid account andthe transferee prepaid account and ii) being generated at the time ofcreation of the transferee prepaid account; determine, via the prepaidaccounts receivable request server, using the retrieved prepaid accountlink data record, the transferor prepaid account that is linked with thetransferee prepaid account; and generating via the prepaid accountsreceivable request server, a prepaid account funds transfer schedulerecord for storage in a schedules database, the prepaid account fundstransfer schedule record indicating a date when the prepaid fundstransfer amount of funds specified in the prepaid account receivablesrequest are to be automatically transferred from the transferor prepaidaccount to the created transferee prepaid account.
 7. The system ofclaim 6, wherein creation of the transferee prepaid account depends onthe transferee user passing a screening test based on the completedprepaid account application.
 8. The system of claim 6, wherein thetransferee prepaid account is created locally.
 9. The system of claim 6,the prepaid accounts receivable request server further configured to:transfer a scheduled transfer amount from the transferor prepaid accountto the created transferee prepaid account according to the generatedprepaid account funds transfer schedule.
 10. The system of claim 9,wherein at least one scheduled funds transfer included in the prepaidaccount funds transfer schedule specifies transferring funds from thetransferee prepaid account to the transferor prepaid account.
 11. Atangible computer readable medium storing processor-issuable prepaidaccount funds transfer instructions to: receive at the prepaid accountsreceivable request server, via an electronic payment processing network,from a transferee user holding a transferee prepaid account, a prepaidaccount receivables request specifying i) a transferee user identifierand ii) a prepaid funds transfer amount to be transferred from atransferor prepaid account of the transferor user to the transfereeprepaid account of the transferee user; in response to receiving theprepaid account receivables request, retrieve, via the prepaid accountsreceivable request server, a prepaid account link data record based onthe received transferee user identifier from a links database, theprepaid link data record i) providing a link between the transferorprepaid account and the transferee prepaid account and ii) beinggenerated at the time of creation of the transferee prepaid account;determine, via the prepaid accounts receivable request server, using theretrieved prepaid account link data record, the transferor prepaidaccount that is linked with the transferee prepaid account; andgenerating, via the prepaid accounts receivable request server, aprepaid account funds transfer schedule record for storage in aschedules database, the prepaid account funds transfer schedule recordindicating a date when the prepaid funds transfer amount of fundsspecified in the prepaid account receivables request are to beautomatically transferred from the transferor prepaid account to thecreated transferee prepaid account.
 12. The medium of claim 11, whereincreation of the transferee prepaid account depends on the transfereeuser passing a screening test based on the completed prepaid accountapplication.
 13. The medium of claim 11, wherein the transferee prepaidaccount is created locally.
 14. The medium of claim 11, further storingprocessing instructions to: transfer a scheduled transfer amount fromthe transferor prepaid account to the created transferee prepaid accountaccording to the generated prepaid account funds transfer schedule. 15.The medium of claim 14, wherein at least one scheduled funds transferincluded in the prepaid account funds transfer schedule specifiestransferring funds from the transferee prepaid account to the transferorprepaid account.